Alexander Kanavin
2024-Oct-16 10:45 UTC
regress/key-options.sh: should expire much later than in 2038
Hello, Testing systems for Y2038 safety is done by setting the clock to after 2038, and then running all available test suites. This however requires that actual Y2038 issues are not masked by key expiry errors (when tests hardcode expiry dates), and this is what happens in this particular test. I've submitted a fix here: https://github.com/openssh/openssh-portable/pull/425 and here: https://bugzilla.mindrot.org/show_bug.cgi?id=3684 but no one's reacting so I thought I try this channel as well. Thanks, Alex
Reasonably Related Threads
- [Bug 3684] New: regress/key-options.sh: update future key expiry date to far in the future
- [Bug 2856] New: key-options.sh fails when pty /dev/ttyp1 is not owned by testing user
- [Bug 3787] New: Files with a creation date later than January 19, 2038 are not displayed in 32-bit sftp
- Working around the year 2038 bug in Ruby''s Time class?
- Antwort: Password about to expire -- Turn Windlows Client Password Ageing Off?