[19060] in Kerberos_V5_Development
Re: krb5_timestamp and 2038
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Dec 1 10:50:50 2014
Message-ID: <547C8E51.5080607@mit.edu>
Date: Mon, 01 Dec 2014 10:50:41 -0500
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Tomas Kuthan <tomas.kuthan@oracle.com>, krbdev@mit.edu
In-Reply-To: <547C4C57.8020205@oracle.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 12/01/2014 06:09 AM, Tomas Kuthan wrote:
> as you all probably know, krb5_timestamp currently represented as 32-bit
> signed integer will overflow in 2038.
>
> Is there already a plan in place to fix it?
> What is the most likely fix, will krb5_timestamp be made unsigned, or
> 64-bit?
My current plan is to add API functions to convert from krb5_timestamp
to time_t, and use them internally wherever we do time computations. On
systems with 64-bit time_t, negative krb5_timestamp values will be used
to represent times between 2038 and 2106.
> Is there a timeline?
Nothing definite, but we can't wait too long since people already bump
into this occasionally.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
