From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: selinux@tycho.nsa.gov, Russell Coker <russell@coker.com.au>
Subject: Re: suggestion to help transition to selinux: dynamic loading of libselinux
Date: Tue, 18 May 2004 19:11:39 +0000 [thread overview]
Message-ID: <20040518191139.GN24917@lkcl.net> (raw)
In-Reply-To: <1084898046.28966.100.camel@moss-spartans.epoch.ncsc.mil>
On Tue, May 18, 2004 at 12:34:06PM -0400, Stephen Smalley wrote:
> On Sat, 2004-05-15 at 19:26, Luke Kenneth Casson Leighton wrote:
> > idea: make all the modifications to e.g. coreutils, login etc.
> > compile with the header files but not necessarily _need_
> > libselinux at run-time.
>
> Interestingly, this issue just came up on the userlinux mailing list;
> someone noticed that upon doing an apt-get update, they pulled in
> libselinux1. After a bit of investigation, they found that this was due
> to updating gdm, because the SELinux patch for gdm is already
> upstreamed.
ah ha! great! so it's begun.
> Note of caution: Some people still build /sbin/init statically, I
> think, and we don't want to prevent people from doing so just for
> SELinux. The current patches allow for that; if we rewrite them to use
> dlopen, won't that be a problem?
hm.
yes.
you'd need two packages with the same name - two compile-time
#ifdef things - to solve that one.
all in all, i'd say the pros and cons weigh against a rewrite.
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 19:48 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
2004-05-18 16:34 ` Stephen Smalley
2004-05-18 19:11 ` Luke Kenneth Casson Leighton [this message]
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=20040518191139.GN24917@lkcl.net \
--to=lkcl@lkcl.net \
--cc=russell@coker.com.au \
--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.