All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Todd Miller <Tmiller@tresys.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: genhomedircon is broken in libsemanage
Date: Wed, 30 Jan 2008 09:52:45 -0500	[thread overview]
Message-ID: <47A08F3D.6040008@manicmethod.com> (raw)
In-Reply-To: <47A089EC.6020607@redhat.com>

Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Joshua Brindle wrote:
>   
>> Todd Miller wrote:
>>     
>>> Daniel J Walsh wrote:
>>>  
>>>       
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Adding
>>>>
>>>> mythtv:x:1004:1004::/var/lib/mythtv:/bin/bash
>>>>
>>>> To /etc/passwd causes the labeling to get all screwed up.  This would
>>>> report an error when we used the python version of genhomedircon and
>>>> not foul up the labeling by checking if there was a label for /var/lib
>>>> already in the file_context file. (Boy do I love python.  :^))
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=430195
>>>>
>>>> Dan
>>>>     
>>>>         
>>> That shouldn't be hard to add to genhomedircon.c.  I'll take a look.
>>>   
>>>       
>> So, Todd is about to send a patch to fix this but I want to point out
>> that I'm adverse to this sort of thing. There is a minuid and a null
>> shell for a reason, using something above minuid with a valid shell for
>> a non-interactive user is a broken configuration and the fact that we
>> have to work around it is pretty unfortunate.
>>
>> That said the alternative of breaking the system labeling is pretty bad,
>> its probably better to hack around the problem than leave clueless users
>> with broken configurations stranded but I really wish we didn't have to
>> do things like this.
>>
>> *sigh*
>>
>>     
> I think you need to scream in the semanage that this is bad behavior,
> and you can't fix the labels.  The /var/lib situation is bad, but I more
> commonly see admins putting real users in /usr/local or under /var.  We
> need to have a message that explains this is bad and SELinux can not
> handle it.
>   

Well, this is part of the configurability of Linux and thats why people 
love it, right? One solution would be to effectively get rid of 
directory search denials on commodity policies (eg., give all domains 
search on all dirs for the RH policy) then we don't have to worry about 
the "top level home" directory label at all.


--
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.

  reply	other threads:[~2008-01-30 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 15:03 genhomedircon is broken in libsemanage Daniel J Walsh
2008-01-29 18:40 ` Todd Miller
2008-01-29 21:57   ` Joshua Brindle
2008-01-30 14:30     ` Daniel J Walsh
2008-01-30 14:52       ` Joshua Brindle [this message]
2008-01-30 14:59         ` Daniel J Walsh
2008-01-30 15:21           ` Joshua Brindle
2008-01-30 15:33             ` Daniel J Walsh
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29 21:57 Todd C. Miller
2008-01-31 15:13 Todd C. Miller
2008-01-31 15:25 ` Joshua Brindle
2008-02-01 14:23 ` James Antill
2008-02-01 16:52 Todd C. Miller

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=47A08F3D.6040008@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=Tmiller@tresys.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.