From: Paul Moore <paul@paul-moore.com> To: Casey Schaufler <casey@schaufler-ca.com> Cc: casey.schaufler@intel.com, jmorris@namei.org, linux-security-module@vger.kernel.org, selinux@vger.kernel.org, linux-audit@redhat.com, keescook@chromium.org, john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp, stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v33 27/29] Audit: Add record for multiple object security contexts Date: Tue, 15 Mar 2022 21:08:24 -0400 [thread overview] Message-ID: <CAHC9VhSYYy2_cTqZuDrVdoCboMeaUPy0a-1ArRpAhiMYr58r3g@mail.gmail.com> (raw) In-Reply-To: <987800d2-797c-e780-60f5-0e499081572f@schaufler-ca.com> On Tue, Mar 15, 2022 at 8:23 PM Casey Schaufler <casey@schaufler-ca.com> wrote: > On 3/15/2022 4:47 PM, Paul Moore wrote: > > On Thu, Mar 10, 2022 at 7:01 PM Casey Schaufler <casey@schaufler-ca.com> wrote: > >> Create a new audit record AUDIT_MAC_OBJ_CONTEXTS. > >> An example of the MAC_OBJ_CONTEXTS (1421) record is: > >> > >> type=MAC_OBJ_CONTEXTS[1421] > >> msg=audit(1601152467.009:1050): > >> obj_selinux=unconfined_u:object_r:user_home_t:s0 > >> > >> When an audit event includes a AUDIT_MAC_OBJ_CONTEXTS record > >> the "obj=" field in other records in the event will be "obj=?". > >> An AUDIT_MAC_OBJ_CONTEXTS record is supplied when the system has > >> multiple security modules that may make access decisions based > >> on an object security context. > >> > >> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com> > >> --- > >> include/linux/audit.h | 5 +++ > >> include/uapi/linux/audit.h | 1 + > >> kernel/audit.c | 47 +++++++++++++++++++++++ > >> kernel/auditsc.c | 79 ++++++++++++-------------------------- > >> 4 files changed, 77 insertions(+), 55 deletions(-) ... > >> @@ -1373,18 +1362,10 @@ static void show_special(struct audit_context *context, int *call_panic) > >> from_kgid(&init_user_ns, context->ipc.gid), > >> context->ipc.mode); > >> if (osid) { > >> - struct lsmcontext lsmcxt; > >> struct lsmblob blob; > >> > >> lsmblob_init(&blob, osid); > >> - if (security_secid_to_secctx(&blob, &lsmcxt, > >> - LSMBLOB_FIRST)) { > >> - audit_log_format(ab, " osid=%u", osid); > >> - *call_panic = 1; > >> - } else { > >> - audit_log_format(ab, " obj=%s", lsmcxt.context); > >> - security_release_secctx(&lsmcxt); > >> - } > >> + audit_log_object_context(ab, &blob); > > While we lose the "osid=X" in case of failure, the secid/SID is a > > private kernel value meaning it was always of questionable value. > > I could come up with a change to audit_log_object_context() that > would put out an osid= in the single security module case. I would > prefer not to if that would be acceptable. What I think you have right now is fine. I thought others might point out the field differences so I was trying to say that the existing code really isn't very useful in case of error, there is no practical way for someone in userspace to do anything meaningful with an osid/secid/SID value as they are transient kernel-private values. My apologies for the confusion. -- paul-moore.com
WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul@paul-moore.com> To: Casey Schaufler <casey@schaufler-ca.com> Cc: john.johansen@canonical.com, selinux@vger.kernel.org, jmorris@namei.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-audit@redhat.com, casey.schaufler@intel.com Subject: Re: [PATCH v33 27/29] Audit: Add record for multiple object security contexts Date: Tue, 15 Mar 2022 21:08:24 -0400 [thread overview] Message-ID: <CAHC9VhSYYy2_cTqZuDrVdoCboMeaUPy0a-1ArRpAhiMYr58r3g@mail.gmail.com> (raw) In-Reply-To: <987800d2-797c-e780-60f5-0e499081572f@schaufler-ca.com> On Tue, Mar 15, 2022 at 8:23 PM Casey Schaufler <casey@schaufler-ca.com> wrote: > On 3/15/2022 4:47 PM, Paul Moore wrote: > > On Thu, Mar 10, 2022 at 7:01 PM Casey Schaufler <casey@schaufler-ca.com> wrote: > >> Create a new audit record AUDIT_MAC_OBJ_CONTEXTS. > >> An example of the MAC_OBJ_CONTEXTS (1421) record is: > >> > >> type=MAC_OBJ_CONTEXTS[1421] > >> msg=audit(1601152467.009:1050): > >> obj_selinux=unconfined_u:object_r:user_home_t:s0 > >> > >> When an audit event includes a AUDIT_MAC_OBJ_CONTEXTS record > >> the "obj=" field in other records in the event will be "obj=?". > >> An AUDIT_MAC_OBJ_CONTEXTS record is supplied when the system has > >> multiple security modules that may make access decisions based > >> on an object security context. > >> > >> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com> > >> --- > >> include/linux/audit.h | 5 +++ > >> include/uapi/linux/audit.h | 1 + > >> kernel/audit.c | 47 +++++++++++++++++++++++ > >> kernel/auditsc.c | 79 ++++++++++++-------------------------- > >> 4 files changed, 77 insertions(+), 55 deletions(-) ... > >> @@ -1373,18 +1362,10 @@ static void show_special(struct audit_context *context, int *call_panic) > >> from_kgid(&init_user_ns, context->ipc.gid), > >> context->ipc.mode); > >> if (osid) { > >> - struct lsmcontext lsmcxt; > >> struct lsmblob blob; > >> > >> lsmblob_init(&blob, osid); > >> - if (security_secid_to_secctx(&blob, &lsmcxt, > >> - LSMBLOB_FIRST)) { > >> - audit_log_format(ab, " osid=%u", osid); > >> - *call_panic = 1; > >> - } else { > >> - audit_log_format(ab, " obj=%s", lsmcxt.context); > >> - security_release_secctx(&lsmcxt); > >> - } > >> + audit_log_object_context(ab, &blob); > > While we lose the "osid=X" in case of failure, the secid/SID is a > > private kernel value meaning it was always of questionable value. > > I could come up with a change to audit_log_object_context() that > would put out an osid= in the single security module case. I would > prefer not to if that would be acceptable. What I think you have right now is fine. I thought others might point out the field differences so I was trying to say that the existing code really isn't very useful in case of error, there is no practical way for someone in userspace to do anything meaningful with an osid/secid/SID value as they are transient kernel-private values. My apologies for the confusion. -- paul-moore.com -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2022-03-16 1:08 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20220310234632.16194-1-casey.ref@schaufler-ca.com> 2022-03-10 23:46 ` [PATCH v33 00/29] LSM: Module stacking for AppArmor Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 01/29] integrity: disassociate ima_filter_rule from security_audit_rule Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-11 10:48 ` kernel test robot 2022-03-11 10:48 ` kernel test robot 2022-03-10 23:46 ` [PATCH v33 02/29] LSM: Infrastructure management of the sock security Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 03/29] LSM: Add the lsmblob data structure Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 04/29] LSM: provide lsm name and id slot mappings Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 05/29] IMA: avoid label collisions with stacked LSMs Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 06/29] LSM: Use lsmblob in security_audit_rule_match Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 07/29] LSM: Use lsmblob in security_kernel_act_as Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 08/29] LSM: Use lsmblob in security_secctx_to_secid Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 09/29] LSM: Use lsmblob in security_secid_to_secctx Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 10/29] LSM: Use lsmblob in security_ipc_getsecid Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 11/29] LSM: Use lsmblob in security_current_getsecid Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 12/29] LSM: Use lsmblob in security_inode_getsecid Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 13/29] LSM: Use lsmblob in security_cred_getsecid Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-11 7:52 ` kernel test robot 2022-03-11 7:52 ` kernel test robot 2022-03-11 9:16 ` kernel test robot 2022-03-11 9:16 ` kernel test robot 2022-03-12 4:50 ` kernel test robot 2022-03-12 4:50 ` kernel test robot 2022-03-10 23:46 ` [PATCH v33 14/29] LSM: Specify which LSM to display Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 15/29] LSM: Ensure the correct LSM context releaser Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 16/29] LSM: Use lsmcontext in security_secid_to_secctx Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 17/29] LSM: Use lsmcontext in security_inode_getsecctx Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 18/29] LSM: security_secid_to_secctx in netlink netfilter Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 19/29] NET: Store LSM netlabel data in a lsmblob Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 20/29] binder: Pass LSM identifier for confirmation Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 21/29] LSM: Extend security_secid_to_secctx to include module selection Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 22/29] Audit: Keep multiple LSM data in audit_names Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 23/29] Audit: Create audit_stamp structure Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 24/29] LSM: Add a function to report multiple LSMs Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 25/29] Audit: Allow multiple records in an audit_buffer Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-15 23:47 ` Paul Moore 2022-03-15 23:47 ` Paul Moore 2022-03-16 0:06 ` Casey Schaufler 2022-03-16 0:06 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 26/29] Audit: Add record for multiple task security contexts Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-15 23:47 ` Paul Moore 2022-03-15 23:47 ` Paul Moore 2022-03-16 0:17 ` Casey Schaufler 2022-03-16 0:17 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 27/29] Audit: Add record for multiple object " Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-15 23:47 ` Paul Moore 2022-03-15 23:47 ` Paul Moore 2022-03-16 0:23 ` Casey Schaufler 2022-03-16 0:23 ` Casey Schaufler 2022-03-16 1:08 ` Paul Moore [this message] 2022-03-16 1:08 ` Paul Moore 2022-03-10 23:46 ` [PATCH v33 28/29] LSM: Add /proc attr entry for full LSM context Casey Schaufler 2022-03-10 23:46 ` Casey Schaufler 2022-03-10 23:46 ` [PATCH v33 29/29] AppArmor: Remove the exclusive flag Casey Schaufler 2022-03-10 23:46 ` 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=CAHC9VhSYYy2_cTqZuDrVdoCboMeaUPy0a-1ArRpAhiMYr58r3g@mail.gmail.com \ --to=paul@paul-moore.com \ --cc=casey.schaufler@intel.com \ --cc=casey@schaufler-ca.com \ --cc=jmorris@namei.org \ --cc=john.johansen@canonical.com \ --cc=keescook@chromium.org \ --cc=linux-audit@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=penguin-kernel@i-love.sakura.ne.jp \ --cc=selinux@vger.kernel.org \ --cc=stephen.smalley.work@gmail.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: linkBe 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.