All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:02:32 +0000	[thread overview]
Message-ID: <20040517220232.GX9378@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:

> Of course we can do this on a per-application basis.  If there is some 
> application for which we can't get the current patches included but for which 
> changes such as you suggest would be accepted then we should definitely do it 
> for that app.
 

> Of course that doesn't require changing libselinux, we could just call dlsym() 
> for every function we want to use.  

ah, you then need to check every pointer to every function
for not being NULL.

it'd be aesthetically better to cut/paste sel-> in front of every
function used rather than have if (fn != NULL) ...

plus you have to check for the success of each dlsym() rather
than just the one.

you can just search for calls to is_selinux_enabled()  and
add the code to do one dlsym() at that point, in fact you
could probably get away with adding a small macro into
libselinux.h that'd do the hard work.


> > p.s. please ask me for clarifications if needed or even for
> > patches rather than go "uhn?  weirdo, weird language, can't
> > even touch a shift key, don't talk to him".  i _want_ selinux
> > to be adapted mainstream by debian, quickly, so talk to me.
> 
> The main thing that is needed for better SE Linux support in Debian is to have 
> more people working on it.  Doing this sort of thing properly requires that 
> most than one person work on it.
 
 count me as a wobbly "in" :)

 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.

  parent reply	other threads:[~2004-05-17 22:05 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 [this message]
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=20040517220232.GX9378@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.