regress/key-options.sh: should expire much later than in 2038

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

 



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
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev



[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux