From owner-freebsd-hackers Sun Jan 27 13:32:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id B2A7237B417 for ; Sun, 27 Jan 2002 13:32:32 -0800 (PST) Received: from lungfish.ntlworld.com ([62.253.152.232]) by mta01-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020127213231.RPOF9422.mta01-svc.ntlworld.com@lungfish.ntlworld.com>; Sun, 27 Jan 2002 21:32:31 +0000 Received: from tuatara.goatsucker.org (tuatara.goatsucker.org [192.168.1.6]) by lungfish.ntlworld.com (8.11.3/8.11.3) with ESMTP id g0RLWTn38155; Sun, 27 Jan 2002 21:32:29 GMT (envelope-from scott@tuatara.goatsucker.org) Received: (from scott@localhost) by tuatara.goatsucker.org (8.11.6/8.11.6) id g0RLW1P15491; Sun, 27 Jan 2002 21:32:01 GMT (envelope-from scott) Date: Sun, 27 Jan 2002 21:32:01 +0000 From: Scott Mitchell To: Volker Stolz Cc: hackers@freebsd.org Subject: Re: PAM, setusercontext, kdm and ports/32273 Message-ID: <20020127213201.D295@localhost> References: <20020126224243.A72777@localhost> <3C534F33.2755EED9@mindspring.com> <20020127115514.A295@localhost> <3C53F08E.66E3E4D5@mindspring.com> <20020127131941.C295@localhost> <20020127213315.A13272@i2.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020127213315.A13272@i2.informatik.rwth-aachen.de>; from stolz@hyperion.informatik.rwth-aachen.de on Sun, Jan 27, 2002 at 09:33:15PM +0100 X-Operating-System: FreeBSD 4.5-RC i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jan 27, 2002 at 09:33:15PM +0100, Volker Stolz wrote: > In local.freebsd-hackers, you wrote: > > I'll accept that there might be bad interactions between PAM and > > setusercontext() that I haven't considered. I'm not familiar enough with > > PAM to know what those would be. > > For example you have to think about which flags to pass to > setusercontext() and when to call it. Doing it whit LOGIN_SETALL > *after* pam_setcred is definitely the wrong choice. Yes, I noticed that xdm takes steps to avoid doing that. > > In any case, hacking kdm is considerably less work, so I might as well do > > that first. > > But beware of those convoluted #ifdefs. In gdm, things where much > easier. It is quite an ugly piece of code... hopefully less so after I'm done with it, however :-) Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott.mitchell@mail.com | 0xAA775B8B | -- Anon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message