From owner-freebsd-current@FreeBSD.ORG  Sat Jan  7 13:53:35 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7ABFA106566B
	for <current@FreeBSD.org>; Sat,  7 Jan 2012 13:53:35 +0000 (UTC)
	(envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242])
	by mx1.freebsd.org (Postfix) with ESMTP id 404BE8FC15
	for <current@FreeBSD.org>; Sat,  7 Jan 2012 13:53:34 +0000 (UTC)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id q07DrRFT021626;
	Sat, 7 Jan 2012 05:53:31 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <201201071353.q07DrRFT021626@gw.catspoiler.org>
Date: Sat, 7 Jan 2012 05:53:27 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: des@FreeBSD.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: current@FreeBSD.org
Subject: couldn't log on to my -CURRENT machine after upgrade to latest PAM
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jan 2012 13:53:35 -0000

I just upgraded my -CURRENT machine for the first time since
mid-November.  When I rebooted, I was surprised that I was unable to log
in via either ssh or directly on the console.  The diagnostics printed
to the console indicated that pam_skey.so was missing.  Since that was
nuked a long time ago, I was puzzled about why it seemed to be required
again.

I was able to get on the machine by booting it single user.  I moved
/etc/pam.conf out of the way and am now able to log in.

Nothing referenced pam_skey under /etc/pam.d, but I found than I had an
ancient copy of /etc/pam.conf that still used pam_skey.  The
documentation says that /etc/pam.conf is only used if
/etc/pam.d/service-name isn't found, and the code appears to agree with
that, however this doesn't seem to be working as expected after the
latest import of PAM.