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 is correct.

In all probability you are hanging on some broken dns server.


Either way, this doesn't sound like a bug in ssh-krb5.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to