All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Alexey S <selinux@udmvt.ru>
Cc: Bandan Das <bandan.das@stratus.com>,
	selinux <selinux@tycho.nsa.gov>,
	"Johnson, Richard" <Richard.Johnson@stratus.com>
Subject: Re: genhomedircon errors with NIS
Date: Tue, 21 Apr 2009 08:00:36 -0400	[thread overview]
Message-ID: <49EDB564.301@redhat.com> (raw)
In-Reply-To: <20090421095354.GG9889@ruber.office.udmvt.ru>

On 04/21/2009 05:53 AM, Alexey S wrote:
> On Mon, Apr 20, 2009 at 03:50:24PM -0400, Daniel J Walsh wrote:
>> On 04/20/2009 03:36 PM, Bandan Das wrote:
>>> ...
>> genhomedircon on RHEL5 is a python script so you can edit it and have it
>> exit on start or ignore /h
>>
>> But if we update policycoreutils, you changes would get overwritten.
>>
>> I believe this works but I never tried it.
>>
>> Add the following to /etc/selinux/semanage.conf and it will use the
>> alternate script instead of the standard
>>
>>
>> [genhomedircon]
>> path = /usr/local/sbin/genhomedircon_modified args = -t $@
>> [end]
>>
>>
>>
>>
>> [genhomedircon]
>> path = /usr/bin/true args = -t $@
>> [end]
>>
>> would cause it to always succeed and do nothing.  ( I think.)
> Wouldn't it be better to not try to autogenerate the list of directories to be labeled
> with home_root_t ?
> Why is that impossible to generate that list once and save it somewhere in /etc/ and allow
> sysadmin to edit that list to suit his needs?
> Make the first autogeneration loud and verbose and document that config everywhere.
> You can't guess every possible system's configuration anyway.
>
Actually I am working on removing genhomedircon all together in the 
upstream.  I would like to force the admins to tell us where the home 
directories for each machine are located.

http://danwalsh.livejournal.com/27571.html

THe semantics of figuring out what a Home dir is and where to put labels 
is very difficult and prone to error, as you are seeing.  So having the 
admin tell us with perhaps a tool to help them would be better then the 
current situation.  But this is for RHEL6 and RHEL5 is not likely to change.

--
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:[~2009-04-21 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 18:54 genhomedircon errors with NIS Bandan Das
2009-04-20 19:08 ` Daniel J Walsh
2009-04-20 19:36   ` Bandan Das
2009-04-20 19:50     ` Daniel J Walsh
2009-04-21  9:53       ` Alexey S
2009-04-21 12:00         ` Daniel J Walsh [this message]
2009-04-21 18:39     ` Bandan Das

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=49EDB564.301@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=Richard.Johnson@stratus.com \
    --cc=bandan.das@stratus.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=selinux@udmvt.ru \
    /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.