All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest policycoreutils patch
Date: Tue, 17 Jan 2006 22:41:19 -0500	[thread overview]
Message-ID: <43CDB8DF.9070100@tresys.com> (raw)
In-Reply-To: <43CDB89C.4030608@redhat.com>

Daniel J Walsh wrote:
> Joshua Brindle wrote:
> 
>> Daniel J Walsh wrote:
>>
>>> Includes Ivan and Russells changes
>>>
>>> Now checks to make sure run as root.
>>
>>
>> while it's probably true that most 'direct' libsemanage sessions need 
>> root that is not necessarily true for policy server so I don't think 
>> there should be a hard coded root check in semanage (aren't we trying 
>> to rely on MAC here anyway?)
> 
> The checks are for genhomedircon and semanage both of which will be 
> prevented from running because of DAC control.
>

why not correctly handle the permission failure instead of hardcoding a 
root check? semanage going through the policy server will not be 
affected by DAC(uid) aside from the permissions on the sock file.

>>>
>>> Also chcat can now manipulate categories of users as well as 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.

  reply	other threads:[~2006-01-18  3:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 20:34 Latest policycoreutils patch Daniel J Walsh
2006-01-18  1:36 ` Joshua Brindle
2006-01-18  1:37 ` Joshua Brindle
2006-01-18  3:40   ` Daniel J Walsh
2006-01-18  3:41     ` Joshua Brindle [this message]
2006-01-18  3:48       ` Daniel J Walsh
2006-01-18  3:51         ` Joshua Brindle
2006-01-18  7:02           ` Ivan Gyurdiev
2006-01-18 15:44             ` Daniel J Walsh
2006-01-18 18:00               ` Ivan Gyurdiev
2006-01-18 18:12                 ` Ivan Gyurdiev
2006-01-18 18:30                   ` Stephen Smalley
2006-01-18 18:36                     ` Ivan Gyurdiev
2006-01-18 18:52                       ` Stephen Smalley
2006-01-18 19:04                         ` Ivan Gyurdiev
2006-01-18 19:32                           ` Stephen Smalley
2006-01-18 19:07                         ` Daniel J Walsh
2006-01-18 19:15                           ` Ivan Gyurdiev
2006-01-18 19:19                             ` Daniel J Walsh
2006-01-18 19:59                               ` Stephen Smalley
2006-01-18 20:01                                 ` Ivan Gyurdiev
2006-01-19 14:27                                   ` Daniel J Walsh
2006-01-18 16:13 ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2006-09-07 13:31 Daniel J Walsh
2006-09-08 14:00 ` Karl MacMillan
2006-09-08 14:33 ` Joshua Brindle
2006-09-08 14:55   ` Karl MacMillan
2006-09-08 14:35 ` Stephen Smalley
2006-09-08 16:37   ` Daniel J Walsh
2006-09-08 20:25     ` Stephen Smalley
2006-09-11 12:25       ` Joshua Brindle
2006-09-12 12:45         ` Karl MacMillan
2006-09-13 15:14       ` Joshua Brindle
2006-11-06 15:25 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=43CDB8DF.9070100@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=dwalsh@redhat.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.