From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>
Cc: selinux@tycho.nsa.gov
Subject: Re: suggestion to help transition to selinux: dynamic loading of libselinux
Date: Mon, 17 May 2004 21:56:01 +0000 [thread overview]
Message-ID: <20040517215601.GW9378@lkcl.net> (raw)
In-Reply-To: <200405180510.40047.russell@coker.com.au>
On Tue, May 18, 2004 at 05:10:40AM +1000, Russell Coker wrote:
> On Sun, 16 May 2004 09:26, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > and i presume that if such programs are compromised, and someone
> > attempts to _stop_ libselinux from being loaded, well then
> > those programs will not be capable of making domain transitions
> > etc. and they will be useless [am i right?]
>
> 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.
oh. eek! of course :) cause libselinux.so to be corrupted and you're
in.
hmmm.... physical security is assumed already (i.e. no boot from
floppy)...
... modification of initscripts "by corruption" an outside chance...
... replacement of initscripts (apt-get install sysvinit) _cannot_
be ruled out...
... therefore the startup process must be secure (no dynamic loading)
i don't know enough to be able to say it would be good, or bad, to
make _some_ programs do dynamic loading of libselinux and some not
do it.
l.
--
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.
next prev parent reply other threads:[~2004-05-17 21:58 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 [this message]
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
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=20040517215601.GW9378@lkcl.net \
--to=lkcl@lkcl.net \
--cc=russell@coker.com.au \
--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.