From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>,
Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Paul Moore <paul@paul-moore.com>
Cc: casey.schaufler@intel.com, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org, Audit-ML <linux-audit@redhat.com>,
Kees Cook <keescook@chromium.org>,
John Johansen <john.johansen@canonical.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v22 06/23] LSM: Use lsmblob in security_secid_to_secctx
Date: Tue, 10 Nov 2020 17:56:17 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.2011101753520.9130@namei.org> (raw)
In-Reply-To: <20201105004924.11651-7-casey@schaufler-ca.com>
On Wed, 4 Nov 2020, Casey Schaufler wrote:
> Change security_secid_to_secctx() to take a lsmblob as input
> instead of a u32 secid. It will then call the LSM hooks
> using the lsmblob element allocated for that module. The
> callers have been updated as well. This allows for the
> possibility that more than one module may be called upon
> to translate a secid to a string, as can occur in the
> audit code.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> Cc: netdev@vger.kernel.org
> Cc: linux-audit@redhat.com
Ditto with this, + audit. Also, you should put primary maintainers on the
To: line or they may miss the email.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2020-11-10 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201105004924.11651-1-casey@schaufler-ca.com>
2020-11-05 0:49 ` [PATCH v22 05/23] LSM: Use lsmblob in security_secctx_to_secid Casey Schaufler
2020-11-10 6:53 ` James Morris
2020-11-05 0:49 ` [PATCH v22 06/23] LSM: Use lsmblob in security_secid_to_secctx Casey Schaufler
2020-11-10 6:56 ` James Morris [this message]
2020-11-05 0:49 ` [PATCH v22 08/23] LSM: Use lsmblob in security_task_getsecid Casey Schaufler
2020-11-05 0:49 ` [PATCH v22 13/23] LSM: Ensure the correct LSM context releaser Casey Schaufler
2020-11-05 0:49 ` [PATCH v22 14/23] LSM: Use lsmcontext in security_secid_to_secctx Casey Schaufler
2020-11-05 0:49 ` [PATCH v22 16/23] LSM: security_secid_to_secctx in netlink netfilter Casey Schaufler
2020-11-10 13:37 ` Pablo Neira Ayuso
2020-11-10 19:26 ` James Morris
2020-11-05 0:49 ` [PATCH v22 17/23] NET: Store LSM netlabel data in a lsmblob Casey Schaufler
2020-11-05 0:49 ` [PATCH v22 20/23] Audit: Add new record for multiple process LSM attributes Casey Schaufler
[not found] <20201104234114.11346-1-casey@schaufler-ca.com>
2020-11-04 23:40 ` [PATCH v22 06/23] LSM: Use lsmblob in security_secid_to_secctx Casey Schaufler
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=alpine.LRH.2.21.2011101753520.9130@namei.org \
--to=jmorris@namei.org \
--cc=casey.schaufler@intel.com \
--cc=casey@schaufler-ca.com \
--cc=fw@strlen.de \
--cc=john.johansen@canonical.com \
--cc=kadlec@netfilter.org \
--cc=keescook@chromium.org \
--cc=linux-audit@redhat.com \
--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=pablo@netfilter.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
--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).