From: David Miller <davem@davemloft.net>
To: paul@paul-moore.com
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: New skb extension for use by LSMs (skb "security blob")?
Date: Wed, 21 Aug 2019 15:50:13 -0700 (PDT) [thread overview]
Message-ID: <20190821.155013.1723892743521935274.davem@davemloft.net> (raw)
In-Reply-To: <CAHC9VhSz1_KA1tCJtNjwK26BOkGhKGbPT7v1O82mWPduvWwd4A@mail.gmail.com>
From: Paul Moore <paul@paul-moore.com>
Date: Wed, 21 Aug 2019 18:00:09 -0400
> I was just made aware of the skb extension work, and it looks very
> appealing from a LSM perspective. As some of you probably remember,
> we (the LSM folks) have wanted a proper security blob in the skb for
> quite some time, but netdev has been resistant to this idea thus far.
>
> If I were to propose a patchset to add a SKB_EXT_SECURITY skb
> extension (a single extension ID to be shared among the different
> LSMs), would that be something that netdev would consider merging, or
> is there still a philosophical objection to things like this?
Unlike it's main intended user (MPTCP), it sounds like LSM's would use
this in a way such that it would be enabled on most systems all the
time.
That really defeats the whole purpose of making it dynamic. :-/
next prev parent reply other threads:[~2019-08-21 22:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 22:00 New skb extension for use by LSMs (skb "security blob")? Paul Moore
2019-08-21 22:50 ` David Miller [this message]
2019-08-22 3:27 ` Paul Moore
2019-08-22 3:54 ` David Miller
2019-08-22 18:50 ` Casey Schaufler
2019-08-22 7:03 ` Florian Westphal
2019-08-22 16:32 ` Paul Moore
2019-08-22 20:10 ` Casey Schaufler
2019-08-22 20:15 ` Florian Westphal
2019-08-22 20:35 ` Casey Schaufler
2019-08-22 21:18 ` David Miller
2019-08-22 21:59 ` Casey Schaufler
2019-08-22 22:28 ` David Miller
2019-08-22 22:34 ` Casey Schaufler
2019-08-22 22:36 ` David Miller
2019-08-23 18:56 ` Casey Schaufler
2019-08-22 21:17 ` David Miller
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=20190821.155013.1723892743521935274.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).