From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: /proc file context
Date: Tue, 8 Oct 2002 16:26:10 +0200 [thread overview]
Message-ID: <20021008162610.B5457@lemuria.org> (raw)
I noticed that the Debian sid default policy seems to be lacking
file_context entries for /proc. Not a problem if you are using procfs.
If you don't, maybe this patch to file_contexts/types.fc is useful
(all types taken from the procfs.te file).
I'm almost certain these file contexts were present in an earlier
default policy, so it's likely that they just were ommitted.
*** /usr/share/selinux/policy/default/file_contexts/types.fc Wed Oct 2 02:12:59 2002
--- types.fc Tue Oct 8 18:17:25 2002
***************
*** 337,339 ****
--- 337,354 ----
#
.*/lost\+found(/.*)? system_u:object_r:lost_found_t
+ #
+ # /proc
+ #
+ /proc(/.*)? system_u:object_r:proc_t
+ /proc/kmsg system_u:object_r:proc_kmsg_t
+ /proc/kcore system_u:object_r:proc_kcore_t
+ /proc/sys(/.*)? system_u:object_r:sysctl_t
+ /proc/sys/fs(/.*)? system_u:object_r:sysctl_fs_t
+ /proc/sys/kernel(/.*)? system_u:object_r:sysctl_kernel_t
+ /proc/sys/kernel/modprobe system_u:object_r:sysctl_modprobe_t
+ /proc/sys/net(/.*)? system_u:object_r:sysctl_net_t
+ /proc/sys/net/unix(/.*)? system_u:object_r:sysctl_net_unix_t
+ /proc/sys/vm(/.*)? system_u:object_r:sysctl_vm_t
+ /proc/sys/dev(/.*)? system_u:object_r:sysctl_dev_t
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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:[~2002-10-08 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 14:26 Tom [this message]
2002-10-08 14:36 ` /proc file context Stephen Smalley
2002-10-08 14:41 ` Tom
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=20021008162610.B5457@lemuria.org \
--to=tom@lemuria.org \
--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.