From: Brett Lentz <blentz@cardomain.com>
To: Steve G <linux_4ever@yahoo.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: I am more worried about open then read and write, SELinux needs open access checks.
Date: Thu, 24 Jan 2008 12:35:23 -0800 [thread overview]
Message-ID: <1201206923.3002.55.camel@blentz> (raw)
In-Reply-To: <964182.26945.qm@web51502.mail.re2.yahoo.com>
On Thu, 2008-01-24 at 10:48 -0800, Steve G wrote:
> > I would like to propose that we add one or more avc's to deal with
> > opening a file. open or open_read open_write.
>
>
> There are situations where apps should only do an open_append to make sure they don't erase anything. syslog, auditd, apache are a few apps that come to mind.
>
> -Steve
>
As far as I'm aware, SELinux, and this requested addition, doesn't
govern _how_ you write, just whether you _can_ write.
_______________________________
Brett Lentz | CarDomain Network
System Administrator
blentz@cardomain.com | tel 206.926.2109 | cell 206.851.6669
http://www.cardomain.com/id/wakko666
"A University without students is like an ointment without a fly."
-- Ed Nather, professor of astronomy at UT Austin
--
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:[~2008-01-24 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 18:48 I am more worried about open then read and write, SELinux needs open access checks Steve G
2008-01-24 20:35 ` Brett Lentz [this message]
2008-01-24 20:43 ` Stephen Smalley
2008-01-24 21:13 ` Daniel J Walsh
-- strict thread matches above, loose matches on Subject: below --
2008-01-23 22:01 Daniel J Walsh
2008-01-24 13:08 ` Stephen Smalley
2008-01-24 13:33 ` Stephen Smalley
2008-01-24 14:59 ` James Morris
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=1201206923.3002.55.camel@blentz \
--to=blentz@cardomain.com \
--cc=linux_4ever@yahoo.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.