Re: [netatalk-admins] Nevermind... fixed it myself. *but*...


Subject: Re: [netatalk-admins] Nevermind... fixed it myself. *but*...
From: a sun (asun@zoology.washington.edu)
Date: Mon Jan 19 1998 - 15:17:02 EST


   Contrary to what the Makefile in sys/linux/Makefile says...

   # if you aren't using pam and are using glibc, you'll need to add -lcrypt
   AFPLIBS= -lcrypt
   ADDLIBS=

   well, I thought RedHet 5.0 does use glibc *and* PAM so I shouldn't
   need -lcrypt according to the above comment. But appearantly I really
   did need -lcrypt since that fixed my netatalk login problems.

actually, it's redhat 5.0 that is wrong here. applications shouldn't
need to link against -lcrypt as specific pam modules which need it
should do so themselves. for example, this is what i get when i do an
ldd against /lib/security/pam_auth_unix.so:
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x40004000)
        libc.so.6 => /lib/libc.so.6 (0x40031000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)

it looks like redhat 5.0 didn't build the pam modules correctly.

-a



This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:30:24 EST