From: Daniel J Walsh <dwalsh@redhat.com>
To: selinux@tycho.nsa.gov
Subject: Why does SELinux treat access(file, W_OK) the same way as write(fd, "XYZ")?
Date: Wed, 20 Sep 2006 11:27:21 -0400 [thread overview]
Message-ID: <45115DD9.2020603@redhat.com> (raw)
Shouldn't the access(file, W_OK) be treated as a getattr rather then a
write access?
Several apps including the kernel do access checks on open file
descriptors and we end up having to write dontaudit rules on {read write
append} when what we really only want to allow the getattr.
Dan
--
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 reply other threads:[~2006-09-20 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 15:27 Daniel J Walsh [this message]
2006-09-20 21:03 ` Why does SELinux treat access(file, W_OK) the same way as write(fd, "XYZ")? Stephen Smalley
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=45115DD9.2020603@redhat.com \
--to=dwalsh@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.