From owner-freebsd-hackers Sun Jan 27 12:33:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 5AB7537B400 for ; Sun, 27 Jan 2002 12:33:23 -0800 (PST) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id g0RKXKq02527; Sun, 27 Jan 2002 21:33:20 +0100 (MET) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.194.33]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id g0RKXKv02522; Sun, 27 Jan 2002 21:33:20 +0100 (MET) Received: from margaux.informatik.rwth-aachen.de (margaux.Informatik.RWTH-Aachen.DE [137.226.194.72]) by hyperion.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1) with ESMTP id VAA03014; Sun, 27 Jan 2002 21:31:51 +0100 (MET) Received: (from stolz@localhost) by margaux.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id VAA13276; Sun, 27 Jan 2002 21:33:15 +0100 (MET) Date: Sun, 27 Jan 2002 21:33:15 +0100 From: Volker Stolz To: Scott Mitchell Cc: hackers@freebsd.org Subject: Re: PAM, setusercontext, kdm and ports/32273 Message-ID: <20020127213315.A13272@i2.informatik.rwth-aachen.de> References: <20020126224243.A72777@localhost> <3C534F33.2755EED9@mindspring.com> <20020127115514.A295@localhost> <3C53F08E.66E3E4D5@mindspring.com> <20020127131941.C295@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20020127131941.C295@localhost> 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 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. > 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. -- Wonderful \hbox (0.80312pt too nice) in paragraph at lines 16--18 Volker Stolz * stolz@i2.informatik.rwth-aachen.de Please use PGP or S/MIME for correspondence! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message