From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: /dev entries which also need to be /.?u?dev'd
Date: Tue, 31 Aug 2004 11:17:33 +0100 [thread overview]
Message-ID: <20040831101733.GC2098@lkcl.net> (raw)
In-Reply-To: <20040831101602.GB2098@lkcl.net>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
duh. having gone to the trouble of producing the list, _let's_ attach
it, shall we?
:)
l.
On Tue, Aug 31, 2004 at 11:16:02AM +0100, Luke Kenneth Casson Leighton wrote:
> the following entries presently marked as /dev need, imo, to also
> be modified to be ":%s/\/dev/\/.?u?dev/g" [in vi].
>
> the reason is as i explained that if someone using udev [with or
> without tmpfs] does a
>
> setfiles /etc/selinux/src/file_contexts/file_contexsts /.dev
>
> then they are buggered, without the above.
>
> for example, /.dev/initctl will suddenly end up with a default_t
> type such that bootup will fail!
>
> also /dev/.udev.tdb was set to default_t as well which could
> have caused problems.
>
> it's all gone pear-shaped, gloop, gloop.
>
> l.
[-- Attachment #2: f --]
[-- Type: text/plain, Size: 1576 bytes --]
program/gpm.fc:/dev/gpmctl -s system_u:object_r:gpmctl_t
program/gpm.fc:/dev/gpmdata -p system_u:object_r:gpmctl_t
program/init.fc:/dev/initctl -p system_u:object_r:initctl_t
program/lpd.fc:/dev/printer -s system_u:object_r:printer_t
program/lpd.fc:/dev/lp.* -c system_u:object_r:printer_device_t
program/lpd.fc:/dev/par.* -c system_u:object_r:printer_device_t
program/lpd.fc:/dev/usb/lp.* -c system_u:object_r:printer_device_t
program/lpd.fc:/dev/usblp.* -c system_u:object_r:printer_device_t
program/lvm.fc:/dev/lvm -c system_u:object_r:fixed_disk_device_t
program/lvm.fc:/dev/mapper/.* -b system_u:object_r:fixed_disk_device_t
program/lvm.fc:/dev/mapper/control -c system_u:object_r:lvm_control_t
program/pppd.fc:/dev/ppp -c system_u:object_r:ppp_device_t
program/pppd.fc:/dev/pppox.* -c system_u:object_r:ppp_device_t
program/pppd.fc:/dev/ippp.* -c system_u:object_r:ppp_device_t
program/syslogd.fc:/dev/log -s system_u:object_r:devlog_t
program/udev.fc:/dev/udev.tbl -- system_u:object_r:udev_tbl_t
program/udev.fc:/dev/\.udev\.tdb -- system_u:object_r:udev_tbl_t
program/vmware.fc:/dev/vmmon -c system_u:object_r:vmware_device_t
program/vmware.fc:/dev/vmnet.* -c system_u:object_r:vmware_device_t
program/vmware.fc:/dev/plex86 -c system_u:object_r:vmware_device_t
program/watchdog.fc:/dev/watchdog -c system_u:object_r:watchdog_device_t
program/xserver.fc:/dev/agpgart -c system_u:object_r:agp_device_t
program/xserver.fc:/dev/dri/.* -c system_u:object_r:dri_device_t
program/xserver.fc:/dev/nvidia.* system_u:object_r:xserver_misc_device_t
next prev parent reply other threads:[~2004-08-31 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 10:16 /dev entries which also need to be /.?u?dev'd Luke Kenneth Casson Leighton
2004-08-31 10:17 ` Luke Kenneth Casson Leighton [this message]
2004-09-02 7:11 ` Russell Coker
2004-09-02 8:11 ` 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=20040831101733.GC2098@lkcl.net \
--to=lkcl@lkcl.net \
--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.