From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kernel_files.patch
Date: Wed, 03 Dec 2008 10:39:43 -0500 [thread overview]
Message-ID: <4936A83F.6020804@redhat.com> (raw)
In-Reply-To: <1228258290.9691.381.camel@gorn>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christopher J. PeBenito wrote:
> On Tue, 2008-11-25 at 17:00 -0500, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F11/kernel_files.patch
>>
>> Fix label of system_map under /boot/efi
>>
>> Add etc_runtime to hosts.deny
>
There are some init scripts that modify the hosts.deny file so it ends
up labeled etc_runtime_t. Forget which one.
> I need justification for this.
>
>> Allow relabel from and to all blk and chr file context. This prevents
>> restorecon from breaking if users have blk files in homedir.
>
> Why would there be device nodes in a user home directory? We can't
> allow device nodes to be relabeled to something that is not a device
> node type.
>
Any kernel developer will end up with chr and block devices in their
homedir, if they run a restorecon or setfiles on their home dir they get
avc messages when they relabel their homedir, with "valid" files in the
homedir. Trying to justify this denial, just ends up with kernel
engineers saying SELinux sucks...
>> Add interfaces to rw_all_files
>>
>> Allow relabel all filesytems to all other files systems (Mount context=)
>
> When/why did the existing rule for this become insufficient?
>
If you bind mount files or file systems mount needs to be able to
read/write the source.
>> Add the ability to delete unlabled file (file_t) tmpreaper needs to be
>> able to delete files left on /tmp that never got labeled on initial label.
>
> I don't have a problem with this, but I think the
> files_delete_isid_type_files() interface needs to be split up. Or put
> the rules into the purge tmp interface.
>
Fine.
>> A few other interfaces
>
> Need explanation for the polyinstantiation change.
>
> files_delete_usr_files() needs to be broken up.
>
Fine
>> Additional mount file ssytem. Any file type can be moved to /tmp.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkk2qD8ACgkQrlYvE4MpobPdKACgoZ6yyvSjrbLoQavDndbQEmML
DU8AoKPX7vhM8puNQgd+kupyiSlu0tkW
=4vtR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-12-03 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 22:00 [refpolicy] kernel_files.patch Daniel J Walsh
2008-12-02 22:51 ` Christopher J. PeBenito
2008-12-03 15:39 ` Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 21:24 Daniel J Walsh
2009-05-21 15:24 Daniel J Walsh
2009-11-12 21:01 Daniel J Walsh
2009-11-24 13:49 ` Christopher J. PeBenito
2010-02-23 22:21 Daniel J Walsh
2010-03-04 19:08 ` Christopher J. PeBenito
2010-03-04 19:17 ` Christopher J. PeBenito
2010-03-05 16:46 ` Daniel J Walsh
2010-03-05 17:12 ` Daniel J Walsh
2010-03-08 11:26 ` Miroslav Grepl
2010-03-08 14:02 ` Christopher J. PeBenito
2010-06-02 20:22 Daniel J Walsh
2010-06-09 13:09 ` Christopher J. PeBenito
2010-06-09 19:10 ` Daniel J Walsh
2010-08-26 22:47 Daniel J Walsh
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=4936A83F.6020804@redhat.com \
--to=dwalsh@redhat.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.