From: Daniel J Walsh <dwalsh@redhat.com>
To: Caleb Case <ccase@tresys.com>
Cc: Chad Sellers <csellers@tresys.com>,
SE Linux <selinux@tycho.nsa.gov>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
Joshua Brindle <method@manicmethod.com>
Subject: Re: SELinux context patch
Date: Thu, 04 Jun 2009 17:15:52 -0400 [thread overview]
Message-ID: <4A283988.2090905@redhat.com> (raw)
In-Reply-To: <150846cc0906041213n79e5e51ex3c72ab2cacb0ce64@mail.gmail.com>
On 06/04/2009 03:13 PM, Caleb Case wrote:
> On Wed, May 20, 2009 at 12:08 PM, Chad Sellers<csellers@tresys.com> wrote:
>> On 5/18/09 2:16 PM, "Daniel J Walsh"<dwalsh@redhat.com> wrote:
>>
>>> This patch adds context files for virtual_domain and virtual_image,
>>> these are both being used to locat the default context to be executed by
>>> svirt.
>>>
>>> I also included the subs patch which I submitted before. This patch
>>> allows us to substitute prefixes to matchpathcon.
>>>
>>> So we can say /export/home == /home
>>>
>>> and
>>>
>>> /web == /var/www
>>
>> I'm surprised that the subs patch didn't get much discussion before. Any
>> thoughts on this? Any worries that it might not meld well with the work
>> currently being done to integrate FCGlob?
>>
>> Thanks,
>> Chad
>>
>
> I don't think it will adversely affect FCGlob integration.
>
> It is going to make it harder to understand what a file will get labeled though.
>
> Might be useful for genhomedircon to generate a .subs file and for
> refpolicy to provide labeling on a selinux user basis for home
> directories:
>
> /root
> /home/unconfined_u
> /home/sysadm_u
> ...
>
> with a .subs:
>
> /home/bob /home/unconfined_u
> /home/sally /home/sysadm_u
> ...
>
> It doesn't support directories with spaces in them.
>
>
> --
> 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.
I would like genhomedircon to just go away totally. Or make it
voluntary, not run in every policy update. getpw() is not guaranteed
to return all users in a Directory and setting up labeling for 100,000
users is just kooky.
The beauty of this patch is it allows admin to take back control of
labeling of homedir. If they want to put home dirs in a random location
and have symlinks from the HOMEDIR labeled in /etc/passwd
This will work. I have had bug reports where people setup different
HOMEDIR links depending on where the machine is at home or in the office
or if they have a remove NFS and a local files.
--
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 prev parent reply other threads:[~2009-06-04 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 18:16 SELinux context patch Daniel J Walsh
2009-05-20 16:08 ` Chad Sellers
2009-06-04 19:13 ` Caleb Case
2009-06-04 20:47 ` Chad Sellers
2009-06-04 21:07 ` Daniel J Walsh
2009-06-04 21:15 ` Daniel J Walsh [this message]
2009-06-05 17:12 ` Christopher J. PeBenito
2009-06-05 17:24 ` Christopher J. PeBenito
2009-06-04 21:14 ` Chad Sellers
2009-06-23 17:10 ` Joshua Brindle
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=4A283988.2090905@redhat.com \
--to=dwalsh@redhat.com \
--cc=ccase@tresys.com \
--cc=cpebenito@tresys.com \
--cc=csellers@tresys.com \
--cc=method@manicmethod.com \
--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.