From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>
Cc: Joshua Brindle <jbrindle@tresys.com>, Greg KH <greg@kroah.com>,
SE Linux <selinux@tycho.nsa.gov>,
fedora-selinux-list@redhat.com
Subject: Re: Fedora and udev
Date: Tue, 24 Aug 2004 15:18:28 +0100 [thread overview]
Message-ID: <20040824141828.GA4698@lkcl.net> (raw)
In-Reply-To: <200408242006.41591.russell@coker.com.au>
On Tue, Aug 24, 2004 at 08:06:41PM +1000, Russell Coker wrote:
> On Tue, 24 Aug 2004 19:28, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > 2) it ONLY set the permissions on the inode NOT on any symlinks and NOT
> > on any directories or subdirectories created.
>
> This part is OK. We have moved to using device_t (the default) as the context
> for all directories and sym-links under /dev.
great, then the policy modifications i've made will be of some
value in pointing you in the right direction, i'll endeavour to
clean them up, sort them out [dammit i just did that and ended
up accidentally deleting it, i _must_ try to stop the habit of
reusing filenames f g h x y and z]
i'm attaching also my modified /etc/init.d/udev file.
as you can see it calls /sbin/restoredevicefiles (sent earlier)
after the make_extra_nodes() call has been made.
why? because it is necessary to do a restorecon on every item
created in /dev, and this is _before_ udev is running, and it is
_to_ get udev running!
i mean, sure, it's fine to grant udev permission to do stuff to
device_t:file/directory instead (or as well?) such that it can
"get started" and then "replace" or "re-restore" permissions on
entries listed in /etc/udev/links.conf, that's another approach
i imagine could be taken.
> > if the file_contexts stuff was somehow pre-munged and
> > transferred into kernel, and the regexp matching code (or
> > something similar) was _also_ transferred into the kernel,
> > then this problem would go away.
>
> I think it's already been decided not to do that.
oh. right. ah well. Next :)
--
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-08-24 14:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 11:25 Fedora and udev Russell Coker
2004-08-22 14:40 ` Luke Kenneth Casson Leighton
2004-08-22 15:29 ` Joshua Brindle
2004-08-22 16:23 ` Luke Kenneth Casson Leighton
2004-08-23 13:04 ` Stephen Smalley
2004-08-22 15:05 ` Joshua Brindle
2004-08-22 17:34 ` Luke Kenneth Casson Leighton
[not found] ` <20040823224444.GI4694@kroah.com>
2004-08-23 22:50 ` Joshua Brindle
2004-08-24 9:28 ` Luke Kenneth Casson Leighton
2004-08-24 10:06 ` Russell Coker
2004-08-24 14:18 ` Luke Kenneth Casson Leighton [this message]
2004-08-24 16:01 ` Luke Kenneth Casson Leighton
2004-08-24 22:23 ` Luke Kenneth Casson Leighton
2004-08-24 11:50 ` Stephen Smalley
2004-08-24 9:41 ` Luke Kenneth Casson Leighton
[not found] ` <20040824163048.GA1715@kroah.com>
2004-08-26 13:57 ` Daniel J Walsh
2004-08-26 13:59 ` Joshua Brindle
[not found] ` <orzn4nuval.fsf@livre.redhat.lsd.ic.unicamp.br>
2004-08-23 2:09 ` Russell Coker
2004-08-23 8:56 ` Luke Kenneth Casson Leighton
2004-08-23 12:04 ` Luke Kenneth Casson Leighton
[not found] ` <1093286952.4101.47.camel@bree.local.net>
2004-08-24 7:25 ` Russell Coker
2004-08-23 2:33 ` 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=20040824141828.GA4698@lkcl.net \
--to=lkcl@lkcl.net \
--cc=fedora-selinux-list@redhat.com \
--cc=greg@kroah.com \
--cc=jbrindle@tresys.com \
--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 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.