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,
A sub second unit would be used. However we use time_t, so currently sub second
time is not possible in Heimdal.
The default unit is seconds.
Skickat från min iPad
19 maj 2014 kl. 05:07 skrev "Henry B Hotz"
mailto:hbh...@oxy.edu>>:
I presume this is for parameters specified the "Java way", an
I presume this is for parameters specified the "Java way", and you do the right
thing when you're reading a krb5.conf file.
I can't personally think of anything where I would care about a sub-second
value. OTOH the standard timeout for kinit is 1 second so it seems possible
someone else might.
Hi All
I am a member of Oracle's Java SE security team, and recently we found a bug
about the inconsistency of the kdc_timeout setting between Java and other
vendors. Java does not support specifying a unit and always treats the value as
milliseconds. While the others support units and when no
Hi All
I am a member of Oracle's Java SE security team, and recently we found a bug
about the inconsistency of the kdc_timeout setting between Java and other
vendors. Java does not support specifying a unit and always treats the value as
milliseconds. While the others support units and when no
