This is a discussion on Re: Fw: SSO with telnet/rlogin/rsh - Kerberos ; "Douglas E. Engert" writes: > From a Kerberos prospective both could be correct. Using the process ID > as part of the cache name allows for session based credentials, so each > telnet session has its own cache. telnetd should ...
"Douglas E. Engert"writes:
> From a Kerberos prospective both could be correct. Using the process ID
> as part of the cache name allows for session based credentials, so each
> telnet session has its own cache.
telnetd should include both the UID and the PID in the cache name. This
works much more smoothly with rpc.gssd and is what I do in pam-krb5.
--
Russ Allbery (rra@stanford.edu)