All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Chad Hanson <chanson@TrustedCS.com>
Cc: Paul Moore <paul.moore@hp.com>, selinux@tycho.nsa.gov
Subject: Re: init running at s9 by default on a MLS system?
Date: Tue, 19 Jul 2005 14:23:20 -0400	[thread overview]
Message-ID: <42DD4518.9080704@redhat.com> (raw)
In-Reply-To: <36282A1733C57546BE392885C0618592AF2836@chaos.tcs.tcs-sec.com>

Chad Hanson wrote:

>Hi Paul,
>
>I would agree the disk partitions should be at s9. The init process should
>probably be at s0. We need to work on providing more updates for this
>policy.
>
>-Chad
>
>  
>
>>-----Original Message-----
>>From: Paul Moore [mailto:paul.moore@hp.com]
>>Sent: Friday, July 15, 2005 12:03 PM
>>To: selinux@tycho.nsa.gov
>>Subject: init running at s9 by default on a MLS system?
>>
>>
>>Hello,
>>
>>I have been playing with Dan Walsh's MLS policy RPM on Fedora Rawhide 
>>and I noticed on the later versions that init is running at level s9 
>>which appears to be causing some problems.  The particular issue I am 
>>dealing with right now is when fsck (as run from 
>>/etc/rc.d/rc.sysinit) 
>>tries to check all of the filesystems in /etc/fstab.  The 
>>problem lies 
>>in the fact that the disk partitions in /dev are all labeled 
>>at s0 and 
>>fsck is trying to open them with write access.  Needless to say the 
>>policy is correct for the strict policy but as soon as you 
>>introduce the 
>>different levels you run into problems.
>>
>>My question is this: should init be running at s9 and if so should we 
>>relabel the partitions to be at s9 as well?
>>
>>-- 
>>. paul moore . . . . . . . . . . . . . . . . . . . . . . . . 
>>. . . . . .
>>. paul.moore@hp.com                                      
>>hewlett packard
>>. (603) 884-5056                                          
>>linux security
>>
>>--
>>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.
>>
>>    
>>
>
>--
>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.
>  
>
How do you specify in policy that kernel_t transitions to init_t but at 
level s0?

Dan

-- 



--
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:[~2005-07-19 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 16:28 init running at s9 by default on a MLS system? Chad Hanson
2005-07-19 18:23 ` Daniel J Walsh [this message]
     [not found] <36282A1733C57546BE392885C0618592AF2A17@chaos.tcs.tcs-sec.com>
2005-07-20 20:26 ` Paul Moore
     [not found] <36282A1733C57546BE392885C0618592AF290B@chaos.tcs.tcs-sec.com>
2005-07-20 18:51 ` Paul Moore
  -- strict thread matches above, loose matches on Subject: below --
2005-07-19 18:34 Chad Hanson
2005-07-19 18:58 ` Daniel J Walsh
2005-07-15 17:03 Paul Moore

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=42DD4518.9080704@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=chanson@TrustedCS.com \
    --cc=paul.moore@hp.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.