On Sun, Nov 18, 2001 at 10:59:01PM -0500, Mike Gerdts wrote: > On Sun, 2001-11-18 at 13:15, Steve Langasek wrote: > > > Having worked extensively with pam_krb5 and the issues you describe, I > > definitely believe this should be changed from a "can/should" to a > > "must". The change will ultimately be driven by application writers who > > need to support the complexities of Kerberos-like systems; I think more > > and more applications are doing things the right way now, precisely > > because of Kerberos. > > For portability sake, I should mention that Solaris 8's pam_krb5 has > rather unique behavior. pam_authenticate updates the ccache, and > pam_setcred with PAM_REINITIALIZE_CRED just dumps core. This is just > the beginning of the troubles with pam_krb5 from Sun, though. I will > try to refrain from off-topic rants about Sun's Kerberos code. Heh. Agreed. There's a reason for making a ccache available in in pam_authenticate(): it may be needed, with Secure NFS, to, say, access .k5login, in, say, pam_acct_mgmt(). And so on. See my comment on the pam-krb5 list about how Solaris expects FILE ccaches named /tmp/krb5_<uid> for Secure NFS... That said, pam_krb5:pam_sm_authenticate() coul create a root-owned, root-read-only FILE ccache (if none existed before) and pam_sm_setcred() could chown() it or, better, re-create it as the actual user. Race conditions would probably be a problem, so this has to be thought through carefully. > Mike > Nico -- -DISCLAIMER: an automatically appended disclaimer may follow. By posting- -to a public e-mail mailing list I hereby grant permission to distribute- -and copy this message.- Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
