From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Christian Göttsche" <cgzones@googlemail.com>
Cc: kadlec@blackhole.kfki.hu, fw@strlen.de, davem@davemloft.net,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
paul@paul-moore.com, sds@tycho.nsa.gov, eparis@parisplace.org,
jmorris@namei.org, serge@hallyn.com, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v3 1/2] netfilter: nf_tables: add SECMARK support
Date: Fri, 28 Sep 2018 11:01:11 +0200 [thread overview]
Message-ID: <20180928090111.7h2rj5vbf5l2dzcy@salvia> (raw)
In-Reply-To: <20180923182616.11398-1-cgzones@googlemail.com>
On Sun, Sep 23, 2018 at 08:26:15PM +0200, Christian Göttsche wrote:
> Add the ability to set the security context of packets within the nf_tables framework.
> Add a nft_object for holding security contexts in the kernel and manipulating packets on the wire.
>
> Convert the security context strings at rule addition time to security identifiers.
> This is the same behavior like in xt_SECMARK and offers better performance than computing it per packet.
>
> Set the maximum security context length to 256.
Applied, thanks Christian.
prev parent reply other threads:[~2018-09-28 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 18:26 [PATCH v3 1/2] netfilter: nf_tables: add SECMARK support Christian Göttsche
2018-09-23 18:26 ` [PATCH v3 2/2] netfilter: nf_tables: add requirements for connsecmark support Christian Göttsche
2018-09-28 9:01 ` Pablo Neira Ayuso
2018-09-28 9:01 ` Pablo Neira Ayuso [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=20180928090111.7h2rj5vbf5l2dzcy@salvia \
--to=pablo@netfilter.org \
--cc=cgzones@googlemail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=eparis@parisplace.org \
--cc=fw@strlen.de \
--cc=jmorris@namei.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
/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