From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Les Bell <lesbell@lesbell.com.au>
Cc: Chris Babcock <cbabcock@luthresearch.com>, selinux@tycho.nsa.gov
Subject: Re: suggestion to help transition to selinux: dynamic loading of libselinux
Date: Tue, 18 May 2004 11:44:14 +0000 [thread overview]
Message-ID: <20040518114414.GA28412@lkcl.net> (raw)
In-Reply-To: <OFC9F6DDFC.10588DF6-ONCA256E98.00360A82@lesbell.com.au>
On Tue, May 18, 2004 at 07:50:34PM +1000, Les Bell wrote:
>
> "Chris Babcock" <cbabcock@luthresearch.com> wrote:
>
> >>
> Does this sound dangerous to anybody else?
> <<
>
> Does the design of SELinux depend on the state machine theory of security,
> i.e. if a system starts in a secure state, and all transitions are secure,
> then the system will remain secure?
personally: i assume so (nothing else makes sense) on the basis that
if you cannot change domain (because either libselinux is unavaiable
or the programs that _use_ libselinux are somehow corrupted and
unavailable) then you can go nowhere and therefore do no damage.
> This design would seem unable to
> support that theory, i.e. until the selinux library is loaded, there are no
> constraints on the state of the machine. Just a thought. . .
yes you are right: there are issues, mentioned by russell,
from initialisation (sysvinit) where if /usr/lib/libselinux.so
is unavaiable (corrupted and in /lost+found) then the initialisation
scripts would need to be modified to halt boot-up if the system
is booted with selinux=1.
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-18 11:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 9:50 suggestion to help transition to selinux: dynamic loading of libselinux Les Bell
2004-05-18 11:44 ` Luke Kenneth Casson Leighton [this message]
2004-05-18 14:07 ` Russell Coker
2004-05-18 14:19 ` Chris Babcock
2004-05-18 14:49 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2004-05-18 6:20 Chris Babcock
2004-05-15 23:26 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
2004-05-18 16:34 ` Stephen Smalley
2004-05-18 19:11 ` Luke Kenneth Casson Leighton
2004-05-18 19:52 ` 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=20040518114414.GA28412@lkcl.net \
--to=lkcl@lkcl.net \
--cc=cbabcock@luthresearch.com \
--cc=lesbell@lesbell.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.