From: Russell Coker <russell@coker.com.au>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: James Morris <jmorris@redhat.com>,
Darrel Goeddel <dgoeddel@TrustedCS.com>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: [patch] selinux_capget()
Date: Mon, 20 Dec 2004 12:16:19 +1100 [thread overview]
Message-ID: <200412201216.23660.russell@coker.com.au> (raw)
In-Reply-To: <20041214162207.5089.qmail@web50205.mail.yahoo.com>
On Wednesday 15 December 2004 03:22, Casey Schaufler <casey@schaufler-ca.com>
wrote:
> > How does the application determine the real
> > effective set?
>
> The short answer is that it doesn't. How do you
> determine if you can really open a file for write
> access? The real world behavior is to check what
> you know about (e.g. UID, mode bits) and hope that
> you'll pass any additinoal constraints (e.g. ACLS,
> capabilities, mount options) that might apply. Then
> try it and check the error return.
Doesn't access(2) deal with ACLs and mount options?
> which is a generalized version of access(2), that
> notoriously unuseful syscall. Needless to say, such
> an inferface is impracticle and would still yield
> false positives.
A faccess(2) syscall would be handy if you are contributing to further POSIX
standards...
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-12-20 1:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 22:32 [patch] selinux_capget() Darrel Goeddel
2004-12-14 0:05 ` James Morris
2004-12-14 0:48 ` Casey Schaufler
2004-12-14 6:09 ` James Morris
2004-12-14 14:37 ` Stephen Smalley
2004-12-14 15:14 ` Stephen Smalley
2004-12-14 15:53 ` Darrel Goeddel
2004-12-14 16:11 ` Stephen Smalley
2004-12-14 16:22 ` Casey Schaufler
2004-12-20 1:16 ` Russell Coker [this message]
2004-12-20 4:51 ` Casey Schaufler
2004-12-20 1:10 ` Russell Coker
2004-12-21 20:32 ` Valdis.Kletnieks
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=200412201216.23660.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=casey@schaufler-ca.com \
--cc=dgoeddel@TrustedCS.com \
--cc=jmorris@redhat.com \
--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 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.