Hi all,
I've been looking at PR ports/32273, after noticing that kdm wasn't picking
up my lang and charset selections from ~/login_conf. The problem seems to
be that kdm thinks PAM and setusercontext() are mutually exclusive, and
it's built with PAM enabled by default. Fixing kdm to DTRT in this
situation -- I'm defining the Right Thing as 'how xdm does it' -- looks to
be pretty simple.
However, this got me thinking -- is the right solution here to have a PAM
module that does the setusercontext(), so programs that already know about
PAM will just work, without needing to know about setusercontext() as well?
I can see that causing problems with programs (login, xdm, etc.) that
already understand both mechanisms, but they could always not use this
hypothetical pam_setusercontext module, right?
So, is this a worthwhile thing to have? I'm happy to either write the PAM
module or fix kdm, but I'd rather not waste my time learning about PAM
internals if people think this would be a pointless exercise.
I await your pearls of wisdom...
Scott
--
===========================================================================
Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England | 0x54B171B9 | don't get sucked into jet engines"
[EMAIL PROTECTED] | 0xAA775B8B | -- Anon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
