On Wed, Mar 07, 2018 at 04:19:33PM +0800, Jason Zaman wrote:
> On Mon, Mar 05, 2018 at 09:03:10AM -0500, Stephen Smalley wrote:
> > On 03/02/2018 01:49 PM, Chris PeBenito wrote:
> > > I've been able to make SETools dynamically link to libsepol. However,
> > > one challenge is with policycap names.
On Mon, Mar 05, 2018 at 09:03:10AM -0500, Stephen Smalley wrote:
> On 03/02/2018 01:49 PM, Chris PeBenito wrote:
> > I've been able to make SETools dynamically link to libsepol. However,
> > one challenge is with policycap names. They're static libsepol, with
> > nothing that exports them. Can w
On 03/02/2018 01:49 PM, Chris PeBenito wrote:
> I've been able to make SETools dynamically link to libsepol. However,
> one challenge is with policycap names. They're static libsepol, with
> nothing that exports them. Can we either:
>
> * export the sepol_polcap_getname() function, or
> * move
On Fri, Mar 2, 2018 at 10:49 AM, Chris PeBenito wrote:
> I've been able to make SETools dynamically link to libsepol. However, one
> challenge is with policycap names. They're static libsepol, with nothing
> that exports them. Can we either:
>
> * export the sepol_polcap_getname() function, or
