From: Casey Schaufler <casey@schaufler-ca.com>
To: David Howells <dhowells@redhat.com>, Stephen Smalley <sds@tycho.nsa.gov>
Cc: dhowells@redhat.com, "Serge E. Hallyn" <serge@hallyn.com>,
viro@ftp.linux.org.uk, hch@infradead.org,
Trond.Myklebust@netapp.com, casey@schaufler-ca.com,
linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 2/3] CRED: Split the task security data and move part of it into struct cred
Date: Wed, 26 Sep 2007 07:58:32 -0700 (PDT) [thread overview]
Message-ID: <402619.1696.qm@web36606.mail.mud.yahoo.com> (raw)
In-Reply-To: <22215.1190813419@redhat.com>
--- David Howells <dhowells@redhat.com> wrote:
> Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> > Precisely when to use one identity vs. the other though isn't always
> > clear, and the potential for accidental divergence is also a concern.
>
> What should auditing use in audit_filter_rules() when dealing with
> AUDIT_SUBJ_* cases? Should the SUBJ cases use the subjective SID and the
> AUDIT_OBJ_* cases use the objective SID? On the other hand AUDIT_OBJ_* cases
> don't seem to have anything to do with tasks.
I believe that you'll need to audit both sets of credentials.
I think that for audit filtering you will need to have the ability
to filter on either. It's no different from the euid/ruid split.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2007-09-26 14:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 16:17 [PATCH 0/3] Introduce credential record David Howells
2007-09-19 16:17 ` [PATCH 1/3] CRED: Introduce a COW credentials record David Howells
2007-09-19 16:18 ` [PATCH 2/3] CRED: Split the task security data and move part of it into struct cred David Howells
2007-09-19 17:28 ` Casey Schaufler
2007-09-19 22:57 ` David Howells
2007-09-20 16:31 ` Casey Schaufler
2007-09-20 17:17 ` David Howells
2007-09-20 17:33 ` David Howells
2007-09-24 14:00 ` Serge E. Hallyn
2007-09-24 14:21 ` Stephen Smalley
2007-09-24 15:35 ` Serge E. Hallyn
2007-09-24 15:52 ` David Howells
2007-09-26 13:30 ` David Howells
2007-09-26 14:14 ` Stephen Smalley
2007-09-26 14:58 ` Casey Schaufler [this message]
2007-09-19 16:18 ` [PATCH 3/3] CRED: Move the effective capabilities into the cred struct David Howells
2007-09-20 4:11 ` Andrew Morgan
2007-09-20 8:15 ` David Howells
2007-09-20 13:38 ` Trond Myklebust
2007-09-20 15:36 ` Casey Schaufler
2007-09-20 16:09 ` Trond Myklebust
2007-09-26 18:23 ` Al Viro
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=402619.1696.qm@web36606.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=Trond.Myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=viro@ftp.linux.org.uk \
/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