simon-git: putty (main): Jacob Nevins
Commits to Tartarus hosted VCS
tartarus-commits at lists.tartarus.org
Tue Aug 30 18:06:36 BST 2022
TL;DR:
d2e982ef openssh-certs: Avoid C99 strftime() specifiers.
Repository: https://git.tartarus.org/simon/putty.git
On the web: https://git.tartarus.org/?p=simon/putty.git
Branch updated: main
Committer: Jacob Nevins <jacobn at chiark.greenend.org.uk>
Date: 2022-08-30 18:06:36
commit d2e982efa727544b54628e37916c2497fe72cf21
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=d2e982efa727544b54628e37916c2497fe72cf21;hp=baea34a5b2d9cd5734c1f4ebf8f4dc121d227820
Author: Jacob Nevins <jacobn at chiark.greenend.org.uk>
Date: Tue Aug 30 17:27:50 2022 +0100
openssh-certs: Avoid C99 strftime() specifiers.
These were introduced in 34d01e1b65 to pretty-print certificate validity
ranges. But Microsoft's C runtime took a while to catch up with C99 --
stackoverflow claims that VS2013 and earlier don't support these
specifiers -- so it's possible to end up with PuTTY executables that
misdisplay these dates. Also, the mingw-w64 toolchain's -Wformat
complains about these specifiers, at least on Debian buster, presumably
for the same reason.
Since the specifiers in question have exact pre-C99 replacements, it
seems easiest just to use those.
crypto/openssh-certs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
More information about the tartarus-commits
mailing list