From: Florian Westphal <fw@strlen.de>
To: Paul Moore <paul@paul-moore.com>
Cc: Richard Guy Briggs <rgb@redhat.com>,
Florian Westphal <fw@strlen.de>,
linux-audit@redhat.com,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Thomas Graf <tgraf@infradead.org>
Subject: Re: [PATCH V2] audit: normalize NETFILTER_PKT
Date: Fri, 24 Feb 2017 02:50:02 +0100 [thread overview]
Message-ID: <20170224015002.GB12342@breakpoint.cc> (raw)
In-Reply-To: <CAHC9VhTkx2pyRw-b64U=B+VdXUBNXebbQOAAkS60Nw1m96YB3w@mail.gmail.com>
Paul Moore <paul@paul-moore.com> wrote:
> On Thu, Feb 23, 2017 at 12:35 PM, Richard Guy Briggs <rgb@redhat.com> wrote:
> > I had another idea on how to include the sport and dport and that was to
> > use the same identifier for sport/icmptype and also for dport/icmpcode,
> > but you've already said you are not interested.
>
> Not at this point in time since we don't have any good requirements at
> the moment. I would like us to keep this small until we have a better
> idea of how people want to use this, this way we don't end up stuck
> maintaining something that is ill suited for what people actually
> want/use.
Right, I think people that want more info should just use NFLOG to
dump the packet to userspace, extracting all the stuff in kernel is
just a mess.
next prev parent reply other threads:[~2017-02-24 1:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 2:50 [PATCH V2] audit: normalize NETFILTER_PKT Richard Guy Briggs
2017-02-23 5:20 ` Florian Westphal
2017-02-23 15:51 ` Richard Guy Briggs
2017-02-23 16:57 ` Paul Moore
2017-02-23 17:04 ` Richard Guy Briggs
2017-02-23 17:06 ` Paul Moore
2017-02-23 17:13 ` Richard Guy Briggs
2017-02-23 17:14 ` Paul Moore
2017-02-23 17:35 ` Richard Guy Briggs
2017-02-24 0:54 ` Paul Moore
2017-02-24 1:50 ` Florian Westphal [this message]
2017-02-23 17:06 ` Florian Westphal
2017-02-23 17:20 ` Richard Guy Briggs
2017-02-24 1:59 ` Florian Westphal
2017-02-24 5:56 ` Paul Moore
2017-02-23 17:20 ` Steve Grubb
2017-02-23 17:29 ` Richard Guy Briggs
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=20170224015002.GB12342@breakpoint.cc \
--to=fw@strlen.de \
--cc=linux-audit@redhat.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
--cc=tgraf@infradead.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 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.