linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev has had udev_selinux removed - argh!
Date: Thu, 29 Jul 2004 18:50:34 +0000	[thread overview]
Message-ID: <20040729185034.GA1530@kroah.com> (raw)
In-Reply-To: <20040729094717.GE6443@lkcl.net>

On Thu, Jul 29, 2004 at 10:47:17AM +0100, Luke Kenneth Casson Leighton wrote:
> hi there,
> 
> gentoo have pulled udev from their distribution because the
> udev_selinux program has been removed from udev and replaced
> with a /etc/dev.d/default/selinux script.

No they have not.  As the Gentoo udev maintainer, I would have heard
about this :)  I see it in the gentoo tree just fine.

Now as to issues if the "hardened Gentoo" people currently like to use
udev or not, well that is a different issue...

> whilst this is reported as "WorkingForRedHat(tm)", i would
> be very grateful if the functionality could be returned such
> that it can be optionally compiled back in.

Great, send me patches to do this.  I'm not a selinux developer, so I
rely on someone else to support this if they want to.  The previous
patches for selinux in udev were not working, so they were removed.

> i have a question for you: is there the possibility of a race
> condition in between udev creating nodes in /dev, and the
> scripts in /etc/dev.d/default getting at them?

Only if your startup scripts are stupid.  :)

> for example, could /dev/usbtts0 be created if i plug in a USB modem,
> and hotplug or a manual process fire up pppd BEFORE
> /etc/dev.d/default/selinux gets to it?

That's a different question than the one above.
Sure, that could happen, it just proves that udev needs to have selinux
support added into it, to prevent this from happening.

> because if so, things are going to fail unexpectedly.

Yup.  Good luck :)

> how has this issue been addressed in udev, and also, whilst
> i realise that Fedora accept the /etc/dev.d/default/selinux
> change, it should concern you that gentoo do not [and therefore,
> like a lemming oblique stroke sheep, i'd rather not, for my
> debian distro].

Again, patches are welcome.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
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

  reply	other threads:[~2004-07-29 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29  9:47 udev has had udev_selinux removed - argh! Luke Kenneth Casson Leighton
2004-07-29 18:50 ` Greg KH [this message]
2004-07-29 20:40   ` Luke Kenneth Casson Leighton
2004-07-29 20:45 ` Kay Sievers
2004-07-29 22:14   ` Luke Kenneth Casson Leighton
2004-07-30  8:57 ` Marco d'Itri

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=20040729185034.GA1530@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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).