At 9:39 PM +0200 9/9/02, Andi Reisenhofer wrote: > 1) Compiling/linking poppassd gives me errors: > > cd ../password && make all > make[2]: Entering directory `/usr/local/src/qpopper4.0.4/password' > gcc -o poppassd auth_user.o poppassd.o -ldl -lpam \ > ../common/libcommon.a > poppassd.o: In function `chkPass': > /usr/local/src/qpopper4.0.4/password/poppassd.c:1197: undefined reference to > `auth_user' > collect2: ld returned 1 exit status > make[2]: *** [poppassd] Error 1 > make[2]: Leaving directory `/usr/local/src/qpopper4.0.4/password' > make[1]: *** [poppassd] Error 2 > make[1]: Leaving directory `/usr/local/src/qpopper4.0.4/popper' > make: *** [popper_server] Error 2
Try doing a 'make realclean' and then re-run ./configure, but omit the '--enable-specialauth' you added before. You usually don't need to specify this; ./configure generally figures out if it is needed; specifying it when it isn't needed can cause the error you are seeing. > 2) Do I need the the poppassd daemon running to get apop auth. working? No, the two are entirely separate. In fact, poppassd won't even change the apop password (it could be hacked to do so, but you would really want to run it under TLS). > 3) How is the order how qpopper uses the auth. methods or must > I configure that with ./configure script or with the qpoppers -f option in > a config > file. > > e.g. what should I configure if I wanted to use apop and/or pam (ldap) as > auth > method. or can I use always on method at once e.g. apop or pam (ldap). You don't configure this in Qpopper. If a user has an APOP password, Qpopper requires the user to authenticate using APOP and not any other mechanism. > 4) I assume SSL (--with-openssl) can be used for all auth options. Yes, it's independent of authentication.
