From owner-freebsd-current Sun Feb 9 16:38:19 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2C8737B40A for ; Sun, 9 Feb 2003 16:38:17 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85CC043F3F for ; Sun, 9 Feb 2003 16:38:16 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 5A5EC5371; Mon, 10 Feb 2003 01:38:14 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Olivier Dony Cc: Sergey Mokryshev , freebsd-current@freebsd.org Subject: Re: Getting an OpenPAM module to work on 5.0-RELEASE From: Dag-Erling Smorgrav Date: Mon, 10 Feb 2003 01:38:13 +0100 In-Reply-To: <20030210010135.A7711@naboo.blacktrap.net> (Olivier Dony's message of "Mon, 10 Feb 2003 01:01:35 +0100") Message-ID: User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386--freebsd) References: <20030209102306.A6880@naboo.blacktrap.net> <20030209195527.V419-100000@lemori.mokr.ru> <20030210010135.A7711@naboo.blacktrap.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Olivier Dony 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