From: Russell Coker <russell@coker.com.au>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Thomas Hood <jdthood@aglu.demon.nl>,
258725@bugs.debian.org,
"Alexander E. Patrakov" <patrakov@ums.usu.ru>,
SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: Bug#258725: Location of net.agent
Date: Mon, 12 Jul 2004 21:16:36 +1000 [thread overview]
Message-ID: <200407122116.36896.russell@coker.com.au> (raw)
In-Reply-To: <20040712083309.GU4677@lkcl.net>
On Mon, 12 Jul 2004 18:33, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> by recommending a subdirectory, it is possible to do the
> selinux-equivalent of setgid, such that any file in that
> subdirectory will be made writeable to the hotplug scripts.
There are two advantages of a subdirectory for writable files, one is that we
don't have to keep changing the file_contexts file every time a change is
made to hotplug, the other is that on systems with a read-only root only one
sym-link is needed to get those files written to a writable file system.
--
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 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040711145538.GA15954@wonderland.linux.it>
[not found] ` <1089615747.2520.213.camel@localhost.localdomain>
2004-07-12 8:33 ` Bug#258725: Location of net.agent Luke Kenneth Casson Leighton
2004-07-12 11:16 ` Russell Coker [this message]
2004-07-12 19:44 ` Luke Kenneth Casson Leighton
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=200407122116.36896.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=258725@bugs.debian.org \
--cc=jdthood@aglu.demon.nl \
--cc=lkcl@lkcl.net \
--cc=patrakov@ums.usu.ru \
--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.