https://bugzilla.mindrot.org/show_bug.cgi?id=3468
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
It's arguably correct - the validity intervals are defined to operate
in the local TZ.
That being said, it is potentially surprising. I have been thinking of
allowing -V to accept less ambiguous time specifications, specifically:
- raw seconds-since-epoch, as hex (0x...) values
- exact date/times in the UTC TZ, as "UTCYYYYMMDD[HHMMSS]"
Would this help you?
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
It's arguably correct - the validity intervals are defined to operate
in the local TZ.
That being said, it is potentially surprising. I have been thinking of
allowing -V to accept less ambiguous time specifications, specifically:
- raw seconds-since-epoch, as hex (0x...) values
- exact date/times in the UTC TZ, as "UTCYYYYMMDD[HHMMSS]"
Would this help you?
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs