From owner-freebsd-current Mon Apr 29 8:21:25 2002 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 DEFFD37B416; Mon, 29 Apr 2002 08:21:21 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 34B4E5346; Mon, 29 Apr 2002 17:21:20 +0200 (CEST) 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: John Baldwin Cc: current@FreeBSD.org Subject: Re: xdm broken on current References: From: Dag-Erling Smorgrav Date: 29 Apr 2002 17:21:19 +0200 In-Reply-To: Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 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 John Baldwin writes: > Ah, so the bug is my binary is too old and is linked against the wrong PAM. > Ok, my bad then. Well, yes and no. There is a bug in xdm which is exposed by the combination of Linux-PAM and FreeBSD's stock PAM configuration. A slightly different configuration would not trigger it, nor would the current version of OpenPAM. I'd say the blame is evenly spread. 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