From: Joshua Brindle <method@manicmethod.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Patch to libsemanage to remove labeling of /root
Date: Tue, 17 Feb 2009 15:40:10 -0500 [thread overview]
Message-ID: <499B20AA.8050902@manicmethod.com> (raw)
In-Reply-To: <499B2091.8000303@redhat.com>
Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Joshua Brindle wrote:
>> Daniel J Walsh wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Joshua Brindle wrote:
>>>> Daniel J Walsh wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> Policy should label /root with one label and this should not be
>>>>> effected
>>>>> by the passwd database.
>>>>>
>>>>> In Fedora policy we label this as admin_home_t. Having this label vary
>>>>> depending on policy ends up with lines like
>>>>>
>>>>> dontaudit * user_home_t:dir search_dir_perms
>>>>> dontaudit * admin_home_t:dir search_dir_perms
>>>>> dontaudit * sysadmin_home_t:dir search_dir_perms
>>>>> dontaudit * staff_home_t:dir search_dir_perms
>>>>>
>>>>> Labeling this directory as user_home_t, opens the system to possible
>>>>> security risks since some domains have to be able to write to
>>>>> user_home_t when they would never be allowed to write to admin_home_t.
>>>> The comment right above the added lines seems to indicate that was
>>>> suppose to be root before, why is / excluded? Are we going to start a
>>>> huge whitelist for genhomedircon?
>>>>
>>>> if (strcmp(pwent->pw_dir, "/") == 0) {
>>>> /* don't relabel / genhomdircon checked to see
>>>> if root
>>>> * was the user and if so, set his home
>>>> directory to
>>>> * /root */
>>>> continue;
>>>> }
>>> No just /root
>>>
>>> /root should not be labeled based on genhomedircon.
>>>
>> Why are the exact same lines there for "/" then?
>>
>>
> Well I guess we do want to protect / and /root.
>
> Others should be fixed by looking at the parent, so if I added /var as a
> homedir it would blow up saying it conflicts with the previous
> definition of /var.
>
I don't think I understand the problem we are trying to solve here...
--
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-02-17 20:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:43 Patch to libsemanage to remove labeling of /root Daniel J Walsh
2009-02-17 20:25 ` Joshua Brindle
2009-02-17 20:31 ` Daniel J Walsh
2009-02-17 20:32 ` Joshua Brindle
2009-02-17 20:39 ` Daniel J Walsh
2009-02-17 20:40 ` Joshua Brindle [this message]
2009-02-17 21:17 ` Daniel J Walsh
2009-02-18 15:47 ` Joshua Brindle
2009-02-18 16:09 ` Daniel J Walsh
2009-02-18 16:20 ` Joshua Brindle
2009-02-18 16:28 ` Daniel J Walsh
2009-02-18 16:57 ` Daniel J Walsh
2009-02-18 19:21 ` Joshua Brindle
2009-02-18 20:09 ` Daniel J Walsh
2009-02-18 20:15 ` Joshua Brindle
2009-02-18 21:25 ` Daniel J Walsh
2009-02-18 21:42 ` Joshua Brindle
2009-02-27 2:22 ` Russell Coker
2009-02-27 22:08 ` Daniel J Walsh
2009-02-27 23:01 ` Russell Coker
2009-02-28 12:09 ` Dominick Grift
2009-02-28 12:29 ` Daniel J Walsh
2009-02-28 12:39 ` Dominick Grift
2009-02-28 12:17 ` 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=499B20AA.8050902@manicmethod.com \
--to=method@manicmethod.com \
--cc=dwalsh@redhat.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.