On May 18, 10:06am, weijun.w...@oracle.com (Wang Weijun) wrote:
-- Subject: Re: RFR 8036779: sun.security.krb5.KdcComm interprets kdc_timeout
| How about this? I will support "s" and "ms" units ("ms" is not defined by o=
| ther vendors though). But will still try to be a little smart when there is
> On May 18, 2014, at 9:48 PM, chris...@zoulas.com wrote:
>
> On May 18, 10:06am, weijun.w...@oracle.com (Wang Weijun) wrote:
> -- Subject: Re: RFR 8036779: sun.security.krb5.KdcComm interprets kdc_timeout
>
> | How about this? I will support "s" and "ms" units ("ms" is not defined by o=
> | the
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
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.
