From: Casey Schaufler <casey@schaufler-ca.com>
To: David Miller <davem@davemloft.net>
Cc: fw@strlen.de, paul@paul-moore.com, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
casey@schaufler-ca.com
Subject: Re: New skb extension for use by LSMs (skb "security blob")?
Date: Thu, 22 Aug 2019 14:59:37 -0700 [thread overview]
Message-ID: <e2e22b41-2aa1-6a52-107d-e4efd9dcacf4@schaufler-ca.com> (raw)
In-Reply-To: <20190822.141845.217313560870249775.davem@davemloft.net>
On 8/22/2019 2:18 PM, David Miller wrote:
> From: Casey Schaufler <casey@schaufler-ca.com>
> Date: Thu, 22 Aug 2019 13:35:01 -0700
>
>> If the secmark where replaced by a security blob, the u32 secmark field
>> in an sk_buff would be replaced by a void * security field.
> You can already use the secmark to hash to some kind of pointer or other
> object.
Would you really want that used in the most common configuration?
Sure, you *can* do that, but it would be insane to do so.
next prev parent reply other threads:[~2019-08-22 21:59 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
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 [this message]
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=e2e22b41-2aa1-6a52-107d-e4efd9dcacf4@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--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).