Hi, 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? Is there a timeline? Thanks, Tomas