-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Test] Lower the Kerberos principal expiration time #73515
Conversation
KRB5/GSSAPI on Arm32 is unable to handle dates far in the future
Tagging subscribers to this area: @dotnet/ncl, @vcsjones Issue DetailsKRB5/GSSAPI on Arm32 is unable to handle dates far in the future. We don't use the credentials long-term so the expiration could be almost arbitrarily short. Fixes #73343
|
Needs |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! extra-platform looks clean from Kerberos prospective.
Perhaps the 9999 month overflow 32bit somewhere?
Socket and Quic test failures unrelated |
My guess would be something like Y2286 problem where Unix timestamp can overflow. The weird thing is that it didn't fail the CI the same way on x86 Linux. I kept the ARM VM in case we want to run some more tests but for the moment I am happy with consistent results and the explanation backed by the limited experiments / debugger output. |
KRB5/GSSAPI on Arm32 is unable to handle dates far in the future. We don't use the credentials long-term so the expiration could be almost arbitrarily short.
Fixes #73343