From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: mount accessing /dev/cdrom as a symlink
Date: Sat, 28 Aug 2004 19:19:09 +0100 [thread overview]
Message-ID: <20040828181909.GF11546@lkcl.net> (raw)
i had to add this to the mount.te policy in order to allow mount
to actually succeed on a udev-automatically-created /dev/cdrom symlink
(to /dev/hdc which is my ide cdrom drive).
so, the question is: should udev have relabelled that symlink correctly,
or should mount be allowed to read device_t symlinks?
bearing in mind that it's the udev *SCRIPTS* in /etc/udev that
will be creating the symlink, NOT the udevd program, nor the udev
program, nor the udevsend program.
likely to have been /etc/udev/ide-devfs.sh that done it, 'guv.
l.
--- /usr/share/selinux/policy/default.1.14/domains/program/mount.te 2004-08-02 08:28:37.000000000 +0100
+++ domains/program/mount.te 2004-08-28 18:54:24.000000000 +0100
@@ -96,3 +97,6 @@
allow mount_t mnt_t:dir { getattr };
dontaudit mount_t { userdomain kernel_t}:fd use;
can_exec(mount_t, { sbin_t bin_t })
+
+allow mount_t device_t:lnk_file { read };
+ #EXE=/bin/mount NAME=cdrom : read
--
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love. If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
--
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 reply other threads:[~2004-08-28 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 18:19 Luke Kenneth Casson Leighton [this message]
2004-08-29 7:08 ` mount accessing /dev/cdrom as a symlink Russell Coker
2004-08-29 9: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=20040828181909.GF11546@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.