On 05/18/2014 10:36 PM, Wang Weijun wrote: > I do notice MIT's krb5 doc has no kdc_timeout at all.
MIT krb5's sendto_kdc timeouts are all hardcoded and, as far as I can tell, they always have been. Way back in 1.2, there were some global variables which a sufficiently dodgy application could set, but there still doesn't seem to have been a public interface for changing them.
