From owner-freebsd-current Sun Jan 20 16: 9:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 164E737B400 for ; Sun, 20 Jan 2002 16:09:41 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id g0L09Wv91827; Mon, 21 Jan 2002 00:09:32 GMT (envelope-from mark@grondar.za) Received: from grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.org (8.11.6/8.11.6) with ESMTP id g0L09Lt34943; Mon, 21 Jan 2002 00:09:21 GMT (envelope-from mark@grondar.za) Message-Id: <200201210009.g0L09Lt34943@grimreaper.grondar.org> To: Dag-Erling Smorgrav Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: Step5, pam_opie OPIE auth fix for review References: In-Reply-To: ; from Dag-Erling Smorgrav "21 Jan 2002 01:00:05 +0100." Date: Mon, 21 Jan 2002 00:09:21 +0000 From: Mark Murray 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: > > In any case, if I understand what you're trying to do, it can be done > > by returning PAM_SUCCESS if OPIE authentication succeeded, PAM_IGNORE > > if it failed but Unix authentication is still allowed, and > > PAM_AUTH_ERR if OPIE failed and Unix authentication is *not* allowed. > > In that case, if you mark pam_opie "sufficient", pam_unix will run > > only if OPIE authentication failed but allowed Unix authentication to > > proceed. > > Hmm, actually, that won't do. I need to think this over some more. The usual route is YES or NO, with IGNORE reserved for modules which have no authentication (like say, pam_motd, which prints /etc/motd during the pam_session_open() phase). IGNORE may have other uses, but I can't remember them offhand. M -- o Mark Murray \_ FreeBSD Services Limited O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message