#8028 ipadb_ldap_attr_to_krb5_timestamp() isn't 2038-safe
Closed: fixed by abbra. Opened by rharwood.

krb5 expanded our timestamp encoding to handle dates up to 2106 while still using 32-bit integers: https://k5wiki.kerberos.org/wiki/Projects/Timestamps_after_2038

While the current behavior is correct for times before 2038, ipadb_ldap_attr_to_krb5_timestamp() will not handle dates past 2038-01-01 00:00 - and it should because that's not too far away.


Metadata Update from @pcech:
- Issue tagged with: Raven

PR: https://github.com/freeipa/freeipa/pull/5288

master:

  • 4c0398433e5707b6067519f9ada72cb697ae225a ipa-kdb: handle dates up to 2106-02-07 06:28:16

ipa-4-9:

  • 18721cc83035359a2f7d49cfe09e7f4b1376b090 ipa-kdb: handle dates up to 2106-02-07 06:28:16

ipa-4-8:

  • 1f1e7dbe6131b3cdc0ba81b454c7729126bfa6ee ipa-kdb: handle dates up to 2106-02-07 06:28:16

Metadata Update from @abbra:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata