From: Casey Schaufler <casey@schaufler-ca.com>
To: LSM List <linux-security-module@vger.kernel.org>,
SELinux List <selinux@tycho.nsa.gov>,
Audit List <linux-audit@redhat.com>
Subject: Fwd: Re: Upstreaming shared LSM interfaces
Date: Thu, 9 Aug 2007 11:59:27 -0700 (PDT) [thread overview]
Message-ID: <588796.69383.qm@web36604.mail.mud.yahoo.com> (raw)
--- Casey Schaufler <casey@schaufler-ca.com> wrote:
> Date: Thu, 9 Aug 2007 11:43:53 -0700 (PDT)
> From: Casey Schaufler <casey@schaufler-ca.com>
> Subject: Re: Upstreaming shared LSM interfaces
> To: "David P. Quigley" <dpquigl@tycho.nsa.gov>,
> Stephen Smalley <sds@tycho.nsa.gov>, James Morris
> <jmorris@namei.org>,
> David Howells <dhowells@redhat.com>,
> Casey Schaufler <casey@schaufler-ca.com>
>
>
> --- "David P. Quigley" <dpquigl@tycho.nsa.gov> wrote:
>
> > Hello Everyone,
> > Between Casey's Audit patches, the FS-Cache patches and the Labeled NFS
> > patches there are a bunch of new LSM interfaces being proposed that some
> > combination of us seem to need. I would like to propose that we agree on
> > the interfaces and send them to James to be upstreamed. The interfaces
> > and the proposed prototypes are listed below
>
> I was wrong to propose the hooks that get the secids to feed to
> the audit system. I had hoped that I could contain the scope of
> the changes required to the audit system to pull SELinux dependencies
> out by allowing the continued use of secids in that case. I see
> now the error in my ways and will shortly proposed an alternative
> patch set for the deselinixifation of audit.
>
> The secid is an internal SELinux data structure (albeit one with
> many favorable characteristics) and the LSM interface ought not
> be exposing it.
>
> > Interfaces:
> >
> > inode_{get,set}secid: From Labeled NFS patches
> > void (*inode_getsecid)(struct inode *inode, u32 *secid);
> > void (*inode_setsecid)(struct inode *inode, u32 secid);
> >
> >
> > ipc_getsecid: From Audit patches
> > void (*ipc_getsecid) (struct kern_ipc_perm *p, u32 *secid);
> >
> > {get,set}_fscreate_secid: From FS-Cache patches
> > u32 (*get_fscreate_secid)(void);
> > u32 (*set_fscreate_secid)(u32 secid);
> >
> >
> > secctx_to_secid: From Labeled NFS patches
> > int (*secctx_to_secid)(u32 *secid, char *secdata, u32 seclen);
> >
> > act_as_{secid,self}: From FS-Cache patches
> > u32 (*act_as_secid)(u32 secid);
> > u32 (*act_as_self)(void);
> >
> >
> > Dave Quigley
> >
> >
> >
>
>
> Casey Schaufler
> casey@schaufler-ca.com
>
>
>
Casey Schaufler
casey@schaufler-ca.com
reply other threads:[~2007-08-09 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=588796.69383.qm@web36604.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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