From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <432730B2.8090005@redhat.com> Date: Tue, 13 Sep 2005 16:04:02 -0400 From: Daniel J Walsh MIME-Version: 1.0 To: Stephen Smalley CC: Darrel Goeddel , SELinux Subject: Re: New ideas on implementation on libsetrans. References: <43271BDA.3060403@redhat.com> <43272C09.3050105@trustedcs.com> <43272E92.4060400@redhat.com> <1126641222.29303.235.camel@moss-spartans.epoch.ncsc.mil> In-Reply-To: <1126641222.29303.235.camel@moss-spartans.epoch.ncsc.mil> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov 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.