From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Darrel Goeddel <dgoeddel@TrustedCS.com>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: New ideas on implementation on libsetrans.
Date: Tue, 13 Sep 2005 16:04:02 -0400 [thread overview]
Message-ID: <432730B2.8090005@redhat.com> (raw)
In-Reply-To: <1126641222.29303.235.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Tue, 2005-09-13 at 15:54 -0400, Daniel J Walsh wrote:
>
>
>>Yes we are having problems with linking against the library and having
>>different plugins to the library just doesnot feel right.
>>
>>
>
>I'm still not sure what the problem is with dlopen'ing libsetrans, and
>letting it take care of the communication (and caching) _if_ any
>translation is desired at all. Why bloat libselinux with that
>infrastructure for people who don't want any label translation?
>
>I understand that the attempt to dlopen a per-policytype libsetrans was
>getting complicated, although I'm not sure why you couldn't just
>dlopen /usr/lib/libsetrans.so symlink and use alternatives to manage
>what that references outside of libselinux.
>
>
>
Most of the people I talk to in Red Hat don't like alternatives. We
can change to just use libsetrans and implement to communication in this
library, but I don't see that as adding much value.
--
--
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:[~2005-09-13 20:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 18:35 New ideas on implementation on libsetrans Daniel J Walsh
2005-09-13 18:59 ` Stephen Smalley
2005-09-13 19:10 ` Luke Kenneth Casson Leighton
2005-09-13 19:44 ` Darrel Goeddel
2005-09-13 19:54 ` Daniel J Walsh
2005-09-13 19:53 ` Stephen Smalley
2005-09-13 20:04 ` Daniel J Walsh [this message]
2005-09-13 20:06 ` Stephen Smalley
2005-09-13 20:33 ` Daniel J Walsh
2005-09-13 20:32 ` Stephen Smalley
2005-09-13 21:19 ` Daniel J Walsh
2005-09-14 13:39 ` Stephen Smalley
2005-09-14 14:15 ` Daniel J Walsh
[not found] ` <20050914192343.GA30138@redhat.com>
2005-09-14 19:51 ` Stephen Smalley
2005-09-14 13:03 ` Steve G
2005-09-14 13:33 ` Stephen Smalley
2005-09-14 17:25 ` Steve G
2005-09-14 17:52 ` Stephen Smalley
2005-09-14 18:01 ` Stephen Smalley
2005-09-16 13:47 ` Luke Kenneth Casson Leighton
2005-09-13 21:22 ` Luke Kenneth Casson Leighton
2005-09-14 11:58 ` Stephen Smalley
2005-09-16 13:59 ` Luke Kenneth Casson Leighton
2005-09-16 17:18 ` Steve G
2005-09-16 17:28 ` Stephen Smalley
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=432730B2.8090005@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=dgoeddel@TrustedCS.com \
--cc=sds@epoch.ncsc.mil \
/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.