Dist:Etch (4.0)
Package: libpam-krb5
Version: 2.6-1
When logging into a system using SSH and authenticating via gssapi-with-mic, the
retain_after_close option to libpam-krb5 is ignored and the ticket
cache is destroyed upon logout.
However, when logging into a system using SSH and standard
Hans Grobler [EMAIL PROTECTED] writes:
Dist:Etch (4.0)
Package: libpam-krb5
Version: 2.6-1
When logging into a system using SSH and authenticating via
gssapi-with-mic, the retain_after_close option to libpam-krb5 is
ignored and the ticket cache is destroyed upon logout.
With
On Fri, 2006-12-15 at 08:53 -0800, Russ Allbery wrote:
With gssapi-with-mic, PAM doesn't obtain the tickets and therefore also
doesn't attempt to destroy them. sshd itself is responsible for both. My
guess is that you're looking for the sshd_config option:
GSSAPICleanupCredentials no
3 matches
Mail list logo
