From owner-freebsd-current Thu Dec 6 15:51:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3739337B41A for ; Thu, 6 Dec 2001 15:51:10 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id D9E4014C53; Fri, 7 Dec 2001 00:51:06 +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: current@freebsd.org Subject: Re: PAM and sudo References: From: Dag-Erling Smorgrav Date: 07 Dec 2001 00:51:06 +0100 In-Reply-To: Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 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 Dag-Erling Smorgrav writes: > Anybody else here having problems with sudo after my recent PAM > commits? I've had complaints from two users so far, but I'm unable to > reproduce the problem. Never mind, I found it, with some assistance from jhb. More evilness in pam_handlers.c - I'll have a fix ready shortly. In the meantime, just 'rmdir /etc/pam.d' as a workaround. 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