On Sun, Jan 12, 2014 at 11:44:56AM -0600, Dustin C. Hatch wrote:
> >> I think I found it. It seemed that the integrated run_init support,
> >> provided
> >> through the runscript_selinux.so library that we provide (for OpenRC)
> >> didn't
> >> use PAM authentication, even when policycoreutils was built with USE="pam".
> >>
> >> This is because the ebuild didn't use the python-r1.eclass BUILD_DIR
> >> location (where the files were compiled earlier in the phase) but the
> >> "normal" ${S} location (which contains the sources). As a result, the "make
> >> install" phase started building the code, without taking the various USE
> >> flags into account, and then installing those files.
[...]
> > Cool, I've kicked off a catalyst rebuild of my SELinux stage[1234] and
> > will deploy a new test VM as soon as its done. I'll let you know how it
> > goes.
> >
> > Thanks again for your help.
> >
> It is indeed working now, thank you. Is there any chance this can be
> backported to 2.1?
Certainly; policycoreutils-2.1.14-r5 is now in tree with the same fix.
Wkr,
Sven Vermeulen
