From owner-freebsd-current Mon Jan 27 9:17:41 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 BD7D837B401 for ; Mon, 27 Jan 2003 09:17:39 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 311E543F7B for ; Mon, 27 Jan 2003 09:17:39 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8EF7F536F; Mon, 27 Jan 2003 18:17:37 +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: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: openpam error from sshd References: <20030125073341.GA11308@rot13.obsecurity.org> From: Dag-Erling Smorgrav Date: Mon, 27 Jan 2003 18:17:37 +0100 In-Reply-To: <20030125073341.GA11308@rot13.obsecurity.org> (Kris Kennaway's message of "Fri, 24 Jan 2003 23:33:41 -0800") Message-ID: Lines: 28 User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2 (i386--freebsd) 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 Kris Kennaway writes: > I've just updated bento to 5.0, and sshd is now giving the following > error every few seconds: > > bento sshd[55737]: in _openpam_check_error_code(): > pam_sm_setcred(): unexpected return value 24 > > Peter says he's seen this elsewhere on the cluster. What's going on? *grumble* it's a bug in one of our PAM modules (krb5, I think), which I never got around to fixing it because it isn't really important. Error 24 is PAM_NO_MODULE_DATA, which isn't an allowed return value for pam_setcred() according to the XSSO, but nobody really cares because anything else than PAM_SUCCESS is an error, so the bug doesn't have any adverse effect other than making OpenPAM bitch so I remember to fix it :) Workaround until I fix the module: in src/lib/libpam/libpam/Makefile, add CFLAGS += -DOPENPAM_RELAX_CHECKS somewhere around the other CFLAGS stuff, then make clean && make && make install. 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