From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: chris@wirex.com, Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: dax@gurulabs.com, Michael Kerrisk <m.kerrisk@gmx.net>,
linux-kernel@vger.kernel.org
Subject: Re: Status of capabilities?
Date: Fri, 28 Jun 2002 08:20:13 -0500 (CDT) [thread overview]
Message-ID: <200206281320.IAA77178@tomcat.admin.navo.hpc.mil> (raw)
Chris Wright <chris@wirex.com>:
> * Jesse Pollard (pollard@tomcat.admin.navo.hpc.mil) wrote:
> >
> > Actually, I think most of that work has already been done by the Linux
> > Security Module project (well, except #7).
>
> The LSM project supports capabilities exactly as it appears in the
> kernel right now. The EA linkage is still missing. Of course, we are
> accepting patches ;-)
Absolutely - I was just meaning that the effort of identifing the location(s)
in the kernel the hooks will have to be to set the capabilities from the EA
reference has been done. And in a central location too. Also, the hooks in the
filesystem will provide the location, if not access to, the EA when they
become available in/to the VFS (at least I hope that's where they end up).
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2002-06-28 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 13:20 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 12:40 Status of capabilities? Michael Kerrisk
2002-06-27 6:05 ` Dax Kelson
2002-06-27 12:57 ` Jesse Pollard
2002-06-27 20:54 ` Chris Wright
2002-06-27 22:52 ` Dax Kelson
2002-07-06 20:56 ` Chris Wright
2002-05-10 6:28 Michael Kerrisk
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=200206281320.IAA77178@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=chris@wirex.com \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kerrisk@gmx.net \
/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