From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, linux-audit@redhat.com,
Eric Paris <eparis@parisplace.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCHv2] netfilter: audit target to record accepted/dropped packets
Date: Fri, 14 Jan 2011 18:51:57 +0000 [thread overview]
Message-ID: <4D309B4D.2010701@googlemail.com> (raw)
In-Reply-To: <20110114165937.GA5759@canuck.infradead.org>
Thomas Graf wrote:
> This patch adds a new netfilter target which creates audit records
> for packets traversing a certain chain.
>
Just a question/suggestion from a (regular) user point of view: Would it
be possible to store the entire packet content or would that prove a bit
too much? If that's possible I am dumping tcpdump (pun intended ;-) )
for good!
next prev parent reply other threads:[~2011-01-14 18:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 15:20 [PATCH] netfilter: audit target to record accepted/dropped packets Thomas Graf
2011-01-14 15:26 ` Eric Paris
2011-01-14 15:31 ` Jan Engelhardt
2011-01-14 15:37 ` Thomas Graf
2011-01-14 15:46 ` Patrick McHardy
2011-01-14 16:19 ` Thomas Graf
2011-01-14 16:49 ` Jan Engelhardt
2011-01-14 16:59 ` [PATCHv2] " Thomas Graf
2011-01-14 17:29 ` Jan Engelhardt
2011-01-14 22:22 ` Thomas Graf
2011-01-14 23:10 ` Michał Mirosław
2011-01-14 23:10 ` Michał Mirosław
2011-01-14 23:19 ` Jan Engelhardt
2011-01-14 23:16 ` Jan Engelhardt
2011-01-14 22:24 ` [PATCHv3] " Thomas Graf
2011-01-14 23:48 ` [PATCHv4] " Thomas Graf
2011-01-14 23:48 ` Thomas Graf
2011-01-15 16:07 ` Patrick McHardy
2011-01-16 17:12 ` [PATCHv3] " Patrick McHardy
2011-01-14 18:51 ` Mr Dash Four [this message]
2011-01-14 19:18 ` [PATCHv2] " Jan Engelhardt
2011-01-14 19:24 ` Eric Paris
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=4D309B4D.2010701@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=eparis@parisplace.org \
--cc=kaber@trash.net \
--cc=linux-audit@redhat.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.