Sounds like your system thinks it can get tickets for the non-kerberos
host, but some kdc is hanging somewhere.
You could edit your krb5.conf either to add a domain realm mapping so
the non-kerberos machine is in some obviouly bogus realm.
Alternatively you could make sure that the kdc information
Package: ssh-krb5
Version: 3.8.1p1-8
Severity: normal
I connect to one machine using kerberos and another ('non-krb-host')
using public-key authentication.
If the kerberos tickets have been destroyed (kdestroy -45), then 'ssh
non-krb-host true' takes about 1.5 seconds. If I get new kerberos
tick
2 matches
Mail list logo
