Greetings
I'm an happy user of qpopper on a DEC OSF/1 platform. Now I'm moving all
the e-mail services (SMTP and POP...IMAP will follows ;-) ) from that
platform to an Intel/Trustix (a secured version of RH Linux:
www.trustix.net) but I've experienced a problemd in the link phase of the
poppassd generation. Trustix uses PAM as its user validation architecture
and I'm using the shadow method.
Hereafter an abstract from the log generated by script command:
-------------------------------------------------------
Script started on Fri Feb 7 19:07:32 2003
root@exd800-01 /sw/qpopper404/qpopper4.0.4# ./configure
--disable-update-abort --enable-apop
--enable-bulldb=/home/bulldb --enable-group-bulls
--enable-home-dir-mail=Mailbox --enable-poppassd
--enable-popuid=pop --enable-server-mode --with-pam
<snip....configure and compile ok>
.
.
.
<snip....configure and compile ok>
cd ../password && make all
make[2]: Entering directory `/sw/qpopper404/qpopper4.0.4/password'
gcc -c -I.. -I. -I.. \
-I../popper -I../common \
-g -O2 -DHAVE_CONFIG_H -DLINUX -DUNIX auth_user.c -o auth_user.o
gcc -c -I.. -I. -I.. \
-I../popper -I../common \
-g -O2 -DHAVE_CONFIG_H -DLINUX -DUNIX poppassd.c -o poppassd.o
gcc -o poppassd auth_user.o poppassd.o -lresolv -ldl -lpam \
../common/libcommon.a
poppassd.o: In function `chkPass':
/sw/qpopper404/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 `/sw/qpopper404/qpopper4.0.4/password'
make[1]: *** [poppassd] Error 2
make[1]: Leaving directory `/sw/qpopper404/qpopper4.0.4/popper'
make: *** [popper_server] Error 2
root@exd800-01 /sw/qpopper404/qpopper4.0.4#
Script done on Fri Feb 7 19:11:56 2003
-------------------------------------------------------
Well, I had a look in the poppassd.c and in the auth_user.c code and in the
last one I've seen that the auth_user function is inside a nested
#ifdef #else condition:
#ifdef SPEC_POP_AUTH
# ifndef USE_PAM
<....a lot of auth_user definition for various unix flavors that do not
use PAM....>
# endif /* USE_PAM */
#else /* not SPEC_POP_AUTH */
< a definition of auth_user for systems that do not use shadow or others
special auth...>
#endif /* SPEC_POP_AUTH */
In other words: I've both SPEC_POP_AUTH and USE_PAM defined, the dirst
'cause I use shadow and the second 'cause Trustix use PAM but this seems
not allowed!
Is it a my fault? Or is it a poppassd coding error?
Please let me know asap
Thank you in advance
----------
Gennaro Esposito
(System & Security Engineer)
MARS Center *****************************
Via E. Gianturco,31 * YES! I SUPPORT *
I-80146 - Napoli - ITALY * *
ph.: +39 081-6042 493 * _/_/ _ _/_/ *
fax...: +39 081-6042 100 * _/_/===x===_/_/ *
mailto:[EMAIL PROTECTED] * _/_/ _/_/ *
http://www.marscenter.it * *
ftp://ftp.marscenter.it *International Space Station*
*****************************
- Re: Problem linking qpopper 404 on Trustix Gennaro Esposito
- Re: Problem linking qpopper 404 on Trustix Clifton Royston
- Re: Problem linking qpopper 404 on Trustix Gennaro Esposito
- Re: Problem linking qpopper 404 on Trustix Ken Hornstein
- Re: Problem linking qpopper 404 on Trustix Randall Gellens
- Re: Problem linking qpopper 404 on Trustix Randall Gellens
- Re: Problem linking qpopper 404 on Trustix Gennaro Esposito
- Re: Problem linking qpopper 404 on Trustix Alan Brown