All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest diff
Date: Sat, 28 Jan 2006 16:17:38 -0500	[thread overview]
Message-ID: <43DBDF72.5050109@redhat.com> (raw)
In-Reply-To: <1138392470.9344.150.camel@sgc>

Christopher J. PeBenito wrote:
> On Fri, 2006-01-27 at 01:37 -0500, Daniel J Walsh wrote:
>   
>> Want to drop sensitivity level on rpm and lvm when run by kernel or 
>> sysadm_t at SystemHigh.
>>     
>
> This seems to contradict what you have in the patch:
>   
What I meant is that when lvm is started by the kernel it is running at 
SystemHigh and there for some files that get
created are SystemHigh.  Specifically a lnk_file in /dev/  Which 
processes try to read and now they get AVC messages.
Turns out that restorecon was broken when restoring symlinks on /dev.  
So fixing restorecon has removed the need for this
range_transition.  Although lvm running at SystemHigh, is probably not 
really needed. 

The other range_transition is to solve an Administrator from running RPM 
from sysadm_t:SystemHigh.  I did this by accident and ended up with some 
files like /etc/ld.so.cache labeled as SystemHigh.  Needless to say this 
caused problems with applications.



>   
>> @@ -86,7 +86,8 @@
>>  ')
>>  
>>  ifdef(`enable_mls',`
>> -# run init with maximum MLS range
>>  range_transition kernel_t init_exec_t s0 - s15:c0.c255;
>> +range_transition kernel_t lvm_exec_t s0 - s15:c0.c255;
>>  range_transition initrc_t auditd_exec_t s15:c0.c255;
>> +range_transition sysadm_t rpm_exec_t s0 - s15:c0.c255;
>>  ')
>>     
>
> Also, why are these needed instead of just using the MLS interfaces?
>
>   


--
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-28 21:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27  6:37 Latest diff Daniel J Walsh
2006-01-27 20:07 ` Christopher J. PeBenito
2006-01-28 21:17   ` Daniel J Walsh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-24 21:58 Latest Diff Daniel J Walsh
2006-01-25 18:41 ` Christopher J. PeBenito
2006-01-17  4:06 latest diff Daniel J Walsh
2006-01-17 18:35 ` Christopher J. PeBenito
2005-05-19 18:51 Latest Diff Daniel J Walsh
2005-05-19 21:36 ` Ivan Gyurdiev
2005-03-22 18:24 Latest diff Daniel J Walsh
2005-03-22 20:20 ` Daniel J Walsh
2005-03-23 18:25 ` James Carter
2005-03-19  6:53 latest diff Daniel J Walsh
2005-03-19 16:14 ` Christopher J. PeBenito
2005-03-19 16:36   ` Daniel J Walsh
2005-03-23 11:10     ` Thomas Bleher
2005-03-23 13:51       ` Stephen Smalley
2005-04-20 12:22     ` Russell Coker
2005-03-21 19:40 ` James Carter

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=43DBDF72.5050109@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cpebenito@tresys.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.