On Wed, 10 Mar 2004 08:58, "Milan P. Stanic" <[EMAIL PROTECTED]> wrote: > [ Sorry, I'm not sure if this list is right place to ask this, but > I can't remember better one ]
The NSA mailing list is another option, but this one is OK. > I'm trying to backport SELinux tools and libraries from unstable to > stable (woody). Well, actually I succeed to build all except coreutils > and sysvinit and installed all under UML and get to the point where > I cannot login in. > I've found problem with pam (backported one) which is compiled on the > woody platform. > > Here is the syslog message: > --------------------------------------------------------------------- > Mar 9 19:29:44 [login] PAM adding faulty module: /lib/security/pam_unix.so > Mar 9 19:29:44 [login] PAM unable to dlopen(/lib/security/pam_selinux.so) > Mar 9 19:29:44 [login] PAM [dlerror: /lib/libselinux.so.1: undefined > symbol: ls etxattr] > --------------------------------------------------------------------- > > I suspect that the problem can be with old glibc (2.2.5) but I'm not > sure. Because that I'd like to ask should I backport glibc from sarge? There have been some changes to the way libxattr works. From memory I think that you needed an extra -l option on the link command line when compiling with old libc6. I can't remember whether it was linking the PAM module or libselinux that needed it (or maybe both). -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]