From: Julien Vehent <julien@linuxwall.info>
To: Thomas Jacob <jacob@internet24.de>
Cc: netfilter@vger.kernel.org
Subject: Re: libpcap (tcpdump) and netfilter (iptables)
Date: Wed, 29 Oct 2008 17:02:28 +0100 [thread overview]
Message-ID: <c7838e4a50bbfe5ac41d4da6f1fec20b@localhost> (raw)
In-Reply-To: <1225293085.13500.5.camel@enterprise.ims-firmen.de>
On Wed, 29 Oct 2008 16:11:25 +0100, Thomas Jacob <jacob@internet24.de>
wrote:
> On Wed, 2008-10-29 at 15:00 +0100, Julien Vehent wrote:
>> Hi,
>>
>> On Wed, 29 Oct 2008 14:20:36 +0100, Pierre LEBRECH
>> <pierre.lebrech@laposte.net> wrote:
>> > Hi,
>> >
>> > It seems that even if I drop some INPUT packets with iptables, tcpdump
>> > still sees these packets arriving on the ethernet interface.
>> >
>> > Could anybody explain me a bit about this?
>>
>> The pcap driver catch the packet before it's processed by netfilter.
>> This is a known issue that has even been used in a rootkit PoC to
>> communicate with the rootkit before the firewall drops the packet.
>
> You may call it a "known issue", I'd called a very useful
> and desirable feature for debugging network packet filters.
>
> If you want to protect your machine against this issue, you
> could simply disable packet sockets, couldn't you?
This is right, "issue" may not be the right term to use here...
Let's call it a "poorly documented feature". And in the case an attacker
has access to the root, the pcap lib should be the least of your
preoccupations...
Considering pcap is never install on production machines (at least, where I
work), I never had to worry about this. :)
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
www.linuxwall.info
prev parent reply other threads:[~2008-10-29 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 13:20 libpcap (tcpdump) and netfilter (iptables) Pierre LEBRECH
2008-10-29 13:56 ` Gáspár Lajos
2008-10-29 13:56 ` Gáspár Lajos
2008-10-29 14:00 ` Julien Vehent
2008-10-29 15:11 ` Thomas Jacob
2008-10-29 16:02 ` Julien Vehent [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7838e4a50bbfe5ac41d4da6f1fec20b@localhost \
--to=julien@linuxwall.info \
--cc=jacob@internet24.de \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox