Path to this page:
Subject: CVS commit: pkgsrc/security/putty
From: Ryo ONODERA
Date: 2025-02-11 11:28:46
Message id: 20250211102846.E24A5FBE0@cvs.NetBSD.org
Log Message:
security/putty: Update to 0.83
Changelog:
0.83 is mostly a bug-fix release, but there are also two new features:
- In SSH, we now support key exchange using the post-quantum
algorithm "ML-KEM", recently standardised by NIST. This is our
second supported post-quantum algorithm, in addition to NTRU Prime
which has been in PuTTY since 0.78. At present, both algorithms are
run in parallel with an existing classical algorithm, just in case.
- On Windows, all of the PuTTY tools' file selector dialogs now
support Unicode file names which don't fit into the system code
page. (But like the rest of the recent Unicode additions, such
filenames still can't reliably be stored in saved sessions.)
Bug fixes in this release include:
- PSFTP's command line option '-b', for handling batch files of PSFTP
commands, was completely broken in 0.82 as a side effect of Unicode
support work. It's now fixed again.
- PuTTY could fail an assertion if an SSH server timed out your
connection while you were still at the login prompt, and then you
selected 'Restart Session'.
- Pageant could crash if you loaded a key into it still encrypted,
started an SSH connection which caused Pageant to prompt for the
key's passphrase, and then abandoned the SSH connection before
entering the passphrase.
- PuTTY could go into a tight loop, consuming CPU and not responding,
if you configured the terminal answerback to the empty string.
- Text entered into some edit boxes in the GUI configuration dialog
was accidentally truncated to 127 characters before writing it into
the saved configuration.
- The default 32-bit Windows builds of PuTTY stopped running on
Windows XP, not intentionally. (Windows would report them as
incompatible.)
- PuTTY's username and password prompts in the terminal accidentally
stopped recognising the keystrokes Ctrl+M and Ctrl+J as ways to
terminate an input line, which broke third-party tools which send
keystrokes to PuTTY and expected those sequences to work.
- Windows PuTTY could fail to update the window width and height
fields in its configuration when resized via the PowerToys
"FancyZones" tool, or any other tool that resize application
windows by the same method.
- On Unix PuTTY and pterm, the keys on the small keypad above the
arrows (Home, End etc) could misbehave in some builds, including
doing nothing at all.
Files: