Issue #8028: ipadb_ldap_attr_to_krb5_timestamp() isn't 2038-safe - freeipa

freeipa

#8028 ipadb_ldap_attr_to_krb5_timestamp() isn't 2038-safe

Closed: fixed 3 years ago by abbra. Opened 4 years ago 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

4 years ago

abbra commented 3 years ago

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

abbra commented 3 years ago

master:

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

abbra commented 3 years ago

ipa-4-9:

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

abbra commented 3 years ago

ipa-4-8:

1f1e7db 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)

3 years ago

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Priority

None

Milestone

None

affects_doc

None

source

None

knownissue

None

type

None

blockedby

None

test_case

None

component

None

blocking

None

on_review

None

keywords

None

test_coverage

None

reviewer

None

external_tracker

None

rhbz

None

tester

None

changelog

None

design

None

freeipa

Source Code

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

Metadata

Raven

#8028 ipadb_ldap_attr_to_krb5_timestamp() isn't 2038-safe

Closed: fixed 3 years ago by abbra. Opened 4 years ago by rharwood.