Date: Sun, 27 Jan 2002 21:33:15 +0100 From: Volker Stolz <stolz@hyperion.informatik.rwth-aachen.de> To: Scott Mitchell <scott.mitchell@mail.com> Cc: hackers@freebsd.org Subject: Re: PAM, setusercontext, kdm and ports/32273 Message-ID: <20020127213315.A13272@i2.informatik.rwth-aachen.de> In-Reply-To: <20020127131941.C295@localhost> References: <20020126224243.A72777@localhost> <3C534F33.2755EED9@mindspring.com> <20020127115514.A295@localhost> <3C53F08E.66E3E4D5@mindspring.com> <20020127131941.C295@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020127213315.A13272>