Date: Mon, 10 Feb 2003 01:38:13 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: Olivier Dony <olivier@blacktrap.net> Cc: Sergey Mokryshev <mokr@mokr.net>, freebsd-current@freebsd.org Subject: Re: Getting an OpenPAM module to work on 5.0-RELEASE Message-ID: <xzpznp5otqi.fsf@flood.ping.uio.no> In-Reply-To: <20030210010135.A7711@naboo.blacktrap.net> (Olivier Dony's message of "Mon, 10 Feb 2003 01:01:35 %2B0100") References: <20030209102306.A6880@naboo.blacktrap.net> <20030209195527.V419-100000@lemori.mokr.ru> <20030210010135.A7711@naboo.blacktrap.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Olivier Dony <olivier@blacktrap.net> writes: > Actually I had patched pam_mysql (on FreeBSD 4.x when pam_mysql was still > working, to be able to use blowfish correctly with FreeBSD's crypt(), but my > problem is really to get an OpenPAM module to work, I even tried to simply > rename the pam_permit one, but have the same problem: openpam_load_module > won't find/open it now matter what... In /usr/src/contrib/openpam/lib/openpam_dynamic.c, change at least the first two instances of PAM_LOG_DEBUG to PAM_LOG_ERROR, then rebuild libpam (cd /usr/src/lib/libpam && make && make install) and try again. OpenPAM will now log messages in /var/log/messages showing why it fails to load your module. My guess is that your module requires a library which you forgot to add to LDADD. BTW, the PAM module makefiles in the tree aren't standalone: they rely on variables set in Makefile.inc one and two levels up. Amongst other things, they add a version number to the dynamic module, and prevent the static version from being installed. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpznp5otqi.fsf>