From owner-freebsd-current Wed Feb 13 17:53: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id 411DE37B416; Wed, 13 Feb 2002 17:53:01 -0800 (PST) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id g1E1pvF27745; Thu, 14 Feb 2002 12:21:57 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 14 Feb 2002 12:22:53 +1030 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id MAA19730; Thu, 14 Feb 2002 12:11:16 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1H6HGADM; Thu, 14 Feb 2002 12:11:13 +1030 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id MAA27375; Thu, 14 Feb 2002 12:11:14 +1030 (CST) Message-ID: <3C6B15C7.28808147@dsto.defence.gov.au> Date: Thu, 14 Feb 2002 12:11:27 +1030 From: "Thyer, Matthew" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Cc: markm@freebsd.org Subject: Re: PAM Error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 >> Yesterday I tried to use SWAT for the first time since the PAM configs were >> moved from /etc/pam.conf and I'm getting the following error: >> >> Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open >> /etc/pam.conf >> >> What do I need to do to fix this? > >Recompile the app. I'm guessing it is linked statically, so is not >picking up the latest libpam. I am still getting this error on both -CURRENT machines I use and these machines *are* fully re-built from source with all applications re-built from an up-to-date ports tree. To reproduce: 1) update your world, kernel and /etc to post new pam 2) rm /etc/pam.conf 3) reboot 4) build ports/security/sudo 5) configure sudo if you haven't already (/usr/local/sbin/visudo as root) 6) type "sudo ls" as your authourised sudo user 7) notice the following on your console: Feb 14 12:05:47 blah sudo: PAM _pam_init_handlers: could not open /etc/pam.conf -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Edinburgh PO Box 1500 EDINBURGH South Australia 5111 IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message