All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: russell@coker.com.au, SE Linux <selinux@tycho.nsa.gov>,
	fedora-selinux-list@redhat.com, gregkh@gentoo.org
Subject: Re: Fedora and udev
Date: Sun, 22 Aug 2004 18:34:57 +0100	[thread overview]
Message-ID: <20040822173457.GD13842@lkcl.net> (raw)
In-Reply-To: <4128B637.8040900@tresys.com>

On Sun, Aug 22, 2004 at 11:05:27AM -0400, Joshua Brindle wrote:
> I posted a patch here that pebenito did a while back for ramfs and lkcl 
> also did one for tmpfs (which may be better for /dev since it's swappable)
> both are mostly cut and paste jobs but they add the necessary support.
> 
> I'd like to reiterate though, that udev support for selinux is *broken*! 
> if the correct policy isn't in place you will cause race conditions
 
 udev is so completely full of race conditions - known to the
 developers even _without_ selinux - that the general consensus
 seems to be that a few more really won't hurt.

 plus, i patched udev (0.030) to add in proper support for selinux
 (attached previously in first response to russell's post).

 that patch ensures (without saving any extra time) that the device
 inodes created, and any directories, _and_ any symlinks (which the
 /etc/udev/default/selinux thing most definitely didn't do) all use
 setfscreatecon rather than doing a restorecon-or-equiv.


 without this patch you will most likely come across issues or end
 up developing an incorrect policy (that ended up with a mismatch
 of default permissions from file_contexts for subdirectories and
 symlinks).

 
 joshua, when you used ramfs, can you remember what the
 fscontext was for /dev when it was mounted?

 l.


--
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.

  reply	other threads:[~2004-08-22 17:23 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 [this message]
     [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
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=20040822173457.GD13842@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=fedora-selinux-list@redhat.com \
    --cc=gregkh@gentoo.org \
    --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.