From: gizmo@giz-works.com (Chris Richards)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] file contexts for /proc/sys/* missing
Date: Wed, 29 Dec 2010 13:32:37 -0600 [thread overview]
Message-ID: <4D1B8CD5.2050705@giz-works.com> (raw)
In-Reply-To: <20101229185611.GA21308@siphos.be>
On 12/29/2010 12:56 PM, Sven Vermeulen wrote:
> Hi all,
>
> My system seems to be unable to give proper security contexts to the "files"
> in /proc/sys/*:
>
> hpl sys # ls -laZ /proc/sys/
> total 0
> dr-xr-xr-x. 1 root wheel system_u:object_r:sysctl_t 0 Dec 29 18:45 .
> dr-xr-xr-x. 154 root root system_u:object_r:proc_t 0 Dec 29 18:45 ..
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:31 abi
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:31 debug
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:31 dev
> dr-xr-xr-x 0 root root ? 0 Dec 29 18:45 fs
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:31 kernel
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:29 net
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:31 sunrpc
> dr-xr-xr-x 0 root root ? 0 Dec 29 19:31 vm
>
Interesting, I have the same behavior here, both on Fedora and my
Gentoo system.
matchpathcon /proc/sys says 'No such file or directory' which suggests
that no contexts are defined for that part of the tree. Interestingly
enough, /proc/sys/fs/binfmt_misc DOES have a context, as do the
contents. This suggests that those files may be labeled by a domtrans
or filetrans.
Someone who knows more than me will have to comment further.
> It seems that kernel.te should generate the necessary contexts, and for some
> other locations (like /proc/net) it does:
>
> dr-xr-xr-x. 6 root wheel staff_u:staff_r:staff_t 0 Dec 29 19:52 .
> dr-x------. 7 root wheel staff_u:staff_r:staff_t 0 Dec 29 19:52 ..
> -r--r--r--. 1 root wheel system_u:object_r:proc_net_t 0 Dec 29 19:52 arp
> -r--r--r--. 1 root wheel system_u:object_r:proc_net_t 0 Dec 29 19:52 connector
> -r--r--r--. 1 root wheel system_u:object_r:proc_net_t 0 Dec 29 19:52 dev
> -r--r--r--. 1 root wheel system_u:object_r:proc_net_t 0 Dec 29 19:52 dev_mcast
> [...]
>
> How do I go about to debug this? I was hoping to put some debugging
> statements along the line of the genfscon macro, but can't find its
> definition anywhere.
>
> Wkr,
> Sven Vermeulen
>
>
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20101229/057e6219/attachment.html
next prev parent reply other threads:[~2010-12-29 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 18:56 [refpolicy] file contexts for /proc/sys/* missing Sven Vermeulen
2010-12-29 19:32 ` Chris Richards [this message]
2011-01-03 21:32 ` Daniel J Walsh
2011-01-03 23:22 ` Sven Vermeulen
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=4D1B8CD5.2050705@giz-works.com \
--to=gizmo@giz-works.com \
--cc=refpolicy@oss.tresys.com \
/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.