From: Russell Coker <russell@coker.com.au>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: policy to allow upgrade of nfs-utils
Date: Mon, 12 Jul 2004 23:02:35 +1000 [thread overview]
Message-ID: <200407122302.35515.russell@coker.com.au> (raw)
In-Reply-To: <1089637087.22449.47.camel@moss-spartans.epoch.ncsc.mil>
On Mon, 12 Jul 2004 22:58, Stephen Smalley <sds@epoch.ncsc.mil> wrote:
> On Sun, 2004-07-11 at 05:04, Russell Coker wrote:
> > A patched version of vi should solve that. In any case if the file gets
> > etc_t then it is just readable to everyone which isn't so bad. The only
> > potential problem is if you edit the file with an unpatched editor and
> > delete all content so that initrc_t will want to append "#" to it.
> >
> > What do you think of the attached patch?
>
> Looks ok, but is it sufficient, i.e. does it only require permission to
> write to the existing /etc/exports, or does it need to be able to unlink
> and re-create the file?
The init script only requires append permission. Of course other programs
need read access which my patch didn't grant, so it's not complete in that
regard.
--
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-07-12 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 3:19 policy to allow upgrade of nfs-utils Russell Coker
2004-07-08 13:14 ` Stephen Smalley
2004-07-09 12:52 ` Russell Coker
2004-07-09 16:53 ` Stephen Smalley
2004-07-11 9:04 ` Russell Coker
2004-07-12 12:58 ` Stephen Smalley
2004-07-12 13:02 ` Russell Coker [this message]
2004-07-12 13:32 ` 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=200407122302.35515.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--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.