From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>
Cc: SE-Linux <selinux@tycho.nsa.gov>,
Linux Hotplug Dev List
<linux-hotplug-devel@lists.sourceforge.net>
Subject: Re: idea - running setfiles out of inetd!
Date: Wed, 18 Aug 2004 16:04:59 +0000 [thread overview]
Message-ID: <20040818160459.GH19646@lkcl.net> (raw)
In-Reply-To: <200408181956.46017.russell@coker.com.au>
On Wed, Aug 18, 2004 at 07:56:46PM +1000, Russell Coker wrote:
> On Wed, 18 Aug 2004 05:47, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > i'd like to canvas people's opinions of running
> > "setfiles -q -s /etc/selinux/contexts/file_contexts" from inetd
>
> Bad idea, anyone can call it.
i've done root-only-accessible unix domain socket stuff before now,
it's necessary to create a directory which is 0500 and then inside
that the socket is 0600 [some unixen don't support permissions on
sockets]
> > the alternative is, in the case of udev, to merge the functionality
> > of udevd and udevsend, such that the file context cacheing can
> > be taken advantage of.
>
> What if udev spawns "setfiles -q -s" and then sends the file names down the
> pipe to it only closing the pipe after a certain time period of no new nodes?
okay, cool...
so.... hey yes, of course.
yes, so that could be run from the main udev process, i get it.
and you exec each udevstart to create the file name, and then
send the same filename down to the "setfiles -q -s".
is using popen() okay to do that?
what implications [on policy writing and also security]
will it have to be running setfiles from inside udev
(bearing in mind that popen involves a pipe and a fork)
... darn! how many programs has udev been split into??? :)
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-08-18 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 19:47 idea - running setfiles out of inetd! Luke Kenneth Casson Leighton
2004-08-18 9:56 ` Russell Coker
2004-08-18 16:04 ` Luke Kenneth Casson Leighton [this message]
2004-08-19 4:55 ` Russell Coker
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=20040818160459.GH19646@lkcl.net \
--to=lkcl@lkcl.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=russell@coker.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).