All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>, selinux@tycho.nsa.gov
Subject: Re: suggestion to help transition to selinux: dynamic loading of libselinux
Date: Tue, 18 May 2004 23:46:36 +1000	[thread overview]
Message-ID: <200405182346.36628.russell@coker.com.au> (raw)
In-Reply-To: <1084879917.28966.11.camel@moss-spartans.epoch.ncsc.mil>

On Tue, 18 May 2004 21:31, Stephen Smalley <sds@epoch.ncsc.mil> wrote:
> On Mon, 2004-05-17 at 15:10, Russell Coker wrote:
> > The first candidate for such changes would be init.  We would have to
> > hard-code a check for selinux=0 in the init source to avoid having init
> > just not enable SE Linux if file system corruption causes libselinux.so
> > to disappear.
> >
> > I think that init is the program that needs such changes most, the
> > current situation makes libselinux one of the most important packages in
> > the system (can't boot without it).
>
> I'm surprised that /sbin/init isn't statically linked in Fedora.
> Rationale?

When fsck, getty, login, /bin/sh, cat etc, and all the other programs that are 
necessary for booting and allowing a root login are dynamically linked it 
doesn't seem to provide much benefit to have init statically linked.

To have all those programs dynamically linked would significantly increase 
disk space for small systems, or require having two versions of each with the 
static version being optional.  So in ancient Linux history it was decided to 
use dynamically linked programs for all of those and almost everyone has 
followed.  Some people have built custom distributions at various times to 
have statically linked /sbin programs but have not apparently received a 
benefit to justify the effort.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

--
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:[~2004-05-18 13:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-15 23:26 suggestion to help transition to selinux: dynamic loading of libselinux Luke Kenneth Casson Leighton
2004-05-17 19:10 ` Russell Coker
2004-05-17 21:56   ` Luke Kenneth Casson Leighton
2004-05-18  0:45     ` Russell Coker
2004-05-18  0:45     ` Valdis.Kletnieks
2004-05-17 22:02   ` Luke Kenneth Casson Leighton
2004-05-18  0:43     ` Russell Coker
2004-05-18 11:31   ` Stephen Smalley
2004-05-18 13:46     ` Russell Coker [this message]
2004-05-18 16:34 ` Stephen Smalley
2004-05-18 19:11   ` Luke Kenneth Casson Leighton
2004-05-18 19:52   ` Russell Coker
  -- strict thread matches above, loose matches on Subject: below --
2004-05-18  6:20 Chris Babcock
2004-05-18  9:50 Les Bell
2004-05-18 11:44 ` Luke Kenneth Casson Leighton
2004-05-18 14:07 ` Russell Coker
2004-05-18 14:19   ` Chris Babcock
2004-05-18 14:49     ` Russell Coker

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=200405182346.36628.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=lkcl@lkcl.net \
    --cc=sds@epoch.ncsc.mil \
    --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.