[Bug 3468] Validity interval changes during Daylight Saving Time

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Thu Aug 11 12:02:46 AEST 2022


Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
             Blocks|                            |3418
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #8 from Damien Miller <djm at mindrot.org> ---
These have been committed and will be in OpenSSH 9.1.

commit b98a42afb69d60891eb0488935990df6ee571c4d
Author: djm at openbsd.org <djm at openbsd.org>
Date:   Thu Aug 11 01:57:50 2022 +0000

    upstream: add some tests for parse_absolute_time(), including cases

    where it is forced to the UTC timezone. bz3468 ok dtucker

    OpenBSD-Regress-ID: ea07ca31c2f3847a38df028ca632763ae44e8759

commit ec1ddb72a146fd66d18df9cd423517453a5d8044
Author: djm at openbsd.org <djm at openbsd.org>
Date:   Thu Aug 11 01:56:51 2022 +0000

    upstream: allow certificate validity intervals, sshsig verification

    times and authorized_keys expiry-time options to accept dates in
the UTC time
    zone in addition to the default of interpreting them in the system
time zone.
    YYYYMMDD and YYMMDDHHMM[SS] dates/times will be interpreted as UTC
    suffixed with a 'Z' character.

    Also allow certificate validity intervals to be specified in raw
    seconds-since-epoch as hex value, e.g. -V 0x1234:0x4567890. This
    is intended for use by regress tests and other tools that call
    ssh-keygen as part of a CA workflow.

    bz3468 ok dtucker

    OpenBSD-Commit-ID: 454db1cdffa9fa346aea5211223a2ce0588dfe13

Referenced Bugs:

[Bug 3418] tracking bug for openssh-9.1
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

More information about the openssh-bugs mailing list