All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>,
	Joshua Brindle <method@manicmethod.com>
Subject: Re: [Fwd: policycoreutils patches]
Date: Fri, 13 Apr 2007 10:39:13 -0400	[thread overview]
Message-ID: <461F9611.9050204@redhat.com> (raw)
In-Reply-To: <1176474662.3986.239.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Fri, 2007-04-13 at 08:53 -0400, Daniel J Walsh wrote:
>   
>> Moved audit2allow to sbin to match audit2why.
>>     
>
> (one patch per message would be nicer)
>
> I actually don't like having so many of the programs in /sbin
> or /usr/sbin, as they aren't in normal user paths and make it more
> painful to find the commands.  And moving them can cause user confusion
> and/or script breakage.  
>
>   
Then for consistency we should move audit2why to the same directory as 
audit2allow.
>> Fix chcat to handle case where there are no categories.
>>
>> Change fixfiles to run setfiles in quiet mode
>>
>> Change genhomedircon to verify context before setting homedir file
>> context. This can happen if you have different user types, where one
>> type has a homedir file context while another one does not.
>>     
>
> Not sure I understand - what does it mean to not have a homedir file
> context for a given user type?   I can understand that multiple user
> roles/types might share the same homedir file context, but not lacking
> one altogether.
>   
Example.  I am about to release a policy creating a guest_t.  This user 
will have very little privs on a system.  The goal of this user type is 
that it will only be used for ssh accounts.  So it will not have a 
guest_mozilla_home_t.  Since it can not even use X-Windows.   Currently 
if I had mozilla policy installed genhomedircon will try to generate 
file context with guest_mozilla_home_t.
>   
>> restorecond init script does not return status properly
>>
>> Fix output of restorecon.c errors to show correct error message.
>>     
>
> Adding a ": %s" with strerror(errno) is fine, but I don't think you want
> to drop the existing error message altogether, as errno isn't always set
> properly. 
>
>   

That error message is misleading and happens on messages that have 
nothing to do " error while labeling files under".



--
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:[~2007-04-13 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 12:53 [Fwd: policycoreutils patches] Daniel J Walsh
2007-04-13 14:31 ` Stephen Smalley
2007-04-13 14:39   ` Daniel J Walsh [this message]
2007-04-13 14:49     ` Stephen Smalley
2007-04-13 14:52       ` Stephen Smalley
2007-04-13 15:10         ` Daniel J Walsh
2007-04-13 15:18           ` Stephen Smalley
2007-04-13 15:17       ` Karl MacMillan
2007-04-13 18:43         ` Stephen Smalley
2007-04-13 18:50           ` Karl MacMillan
2007-04-13 18:33 ` Karl MacMillan
2007-04-24 14:04 ` Stephen Smalley

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=461F9611.9050204@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=method@manicmethod.com \
    --cc=sds@tycho.nsa.gov \
    --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.