All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joubert Berger <joubert@berger-family.org>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: init patch for loading policy
Date: Wed, 22 Oct 2003 18:31:33 -0400	[thread overview]
Message-ID: <1066861893.7534.10.camel@localhost.localdomain> (raw)
In-Reply-To: <3F957200.9040201@redhat.com>

Could you not hard code enough of a policy in the kernel to get init(8)
up and running?  Then let init run a script that loads the complete
policy and then runs /etc/rc.d/rc.sysinit or just have rc.sysinit load
it as it's first step.

--joubert

On Tue, 2003-10-21 at 13:50, Daniel J Walsh wrote:
> Stephen Smalley wrote:
> > On Tue, 2003-10-21 at 10:43, Russell Coker wrote: 
> >   
> > > The results I have so far indicate that this approach has significant 
> > > problems.
> > > 
> > > Diverting /sbin/init with a shell script works better than this.
> > >     
> > Ok, thanks for looking into it.  So what exactly is the problem with
> > diverting /sbin/init again?  
> > 
> >   
> I still believe that the patch to /sbin/init is simple enough that all
> the rest of this stuff is complicating matters.  It allows too many
> ways for someone to make a modification that breaks security.  I have
> updated the files on people.redhat.com/dwalsh to use the modified
> init.  I have passed this by Bill Nottingham (Red Hat maintainer) and
> he is ok with it.
> 
> Of course if someone comes up with a simpler solution we would look at
> it.
> 
> 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:[~2003-10-22 22:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 15:48 init patch for loading policy Russell Coker
2003-10-20  8:21 ` Carsten Grohmann
2003-10-20 18:02 ` Stephen Smalley
2003-10-20 20:10   ` Daniel J Walsh
2003-10-20 20:46     ` Stephen Smalley
2003-10-20 20:56       ` Daniel J Walsh
2003-10-21 12:19         ` Stephen Smalley
2003-10-21  0:52   ` Russell Coker
2003-10-21 12:29     ` Stephen Smalley
2003-10-21 14:43       ` Russell Coker
2003-10-21 14:59         ` Stephen Smalley
2003-10-21 16:00           ` Russell Coker
2003-10-21 18:38             ` Daniel J Walsh
2003-10-21 20:14             ` Bastian Blank
2003-10-21 17:50           ` Daniel J Walsh
2003-10-22 22:31             ` Joubert Berger [this message]
2003-10-23  1:42               ` Russell Coker
2003-10-21 18:07           ` Daniel J Walsh
2003-10-21 18:54             ` Stephen Smalley
2003-10-21 19:56               ` Stephen Smalley
2003-10-21 12:32     ` Stephen Smalley
2003-10-21 13:56       ` Russell Coker
2003-10-20 20:47 ` Bastian Blank
2003-10-21  0:57   ` Russell Coker
2003-10-21  6:26     ` Bastian Blank

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=1066861893.7534.10.camel@localhost.localdomain \
    --to=joubert@berger-family.org \
    --cc=dwalsh@redhat.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.