From owner-freebsd-security  Tue Jan 23 10:40:16 2001
Delivered-To: freebsd-security@freebsd.org
Received: from catapult.web.us.uu.net (catapult.web.us.uu.net [208.211.134.20])
	by hub.freebsd.org (Postfix) with ESMTP id 2997D37B402
	for <freebsd-security@freebsd.org>; Tue, 23 Jan 2001 10:40:00 -0800 (PST)
Received: from catapult.web.us.uu.net (localhost.web.us.uu.net [127.0.0.1])
	by catapult.web.us.uu.net (Postfix) with ESMTP
	id 4A4C83E5B; Tue, 23 Jan 2001 13:39:44 -0500 (EST)
To: "Jacques A. Vidrine" <n@nectar.com>,
	"David J. MacKenzie" <djm@web.us.uu.net>,
	freebsd-security@freebsd.org
Subject: Re: Fwd: [PAM broken design? pam_setcred] 
In-Reply-To: Message from "Jacques A. Vidrine" <n@nectar.com> 
   of "Mon, 22 Jan 2001 08:54:59 CST." <20010122085459.A93103@hamlet.nectar.com> 
Date: Tue, 23 Jan 2001 13:39:44 -0500
From: "David J. MacKenzie" <djm@web.us.uu.net>
Message-Id: <20010123183944.4A4C83E5B@catapult.web.us.uu.net>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


I forwarded your example to the Linux-PAM maintainters, and got back
a reply favoring the approach you intuitively expect; to save the
pam_sm_authenticate() results and call the same modules' pam_sm_setcred()
functions.

The bug report is in the tracking system at:

http://sourceforge.net/bugs/?func=detailbug&bug_id=129775&group_id=6663


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message