Path: csiph.com!weretis.net!feeder8.news.weretis.net!newsfeed.xs3.de!nntp-feed.chiark.greenend.org.uk!ewrotcd!.POSTED.chiark.greenend.org.uk!not-for-mail
From: Simon Tatham <anakin@pobox.com>
Newsgroups: comp.security.ssh
Subject: PuTTY 0.83 is released
Date: Sat, 08 Feb 2025 11:22:14 +0000
Message-ID: <81ed08el5l.fsf@thyestes.tartarus.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: chiark.greenend.org.uk; posting-host="chiark.greenend.org.uk:93.93.131.173"; logging-data="4976"; mail-complaints-to="abuse@chiark.greenend.org.uk"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Cancel-Lock: sha1:j5s1HQ5f2XOeowfLa5ZDSsLq9J0=
Originator: simon@tunnel.thyestes.tartarus.org ([172.31.80.4])
Xref: csiph.com comp.security.ssh:15474

PuTTY version 0.83 is released
------------------------------

All the pre-built binaries, and the source code, are now available
from the PuTTY website at

    https://www.chiark.greenend.org.uk/~sgtatham/putty/

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.

Enjoy using PuTTY!

-- 
for k in [pow(x,37,0x1a1298d262b49c895d47f) for x in [0x50deb914257022de7fff,
0x213558f2215127d5a2d1, 0x90c99e86d08b91218630, 0x109f3d0cfbf640c0beee7,
0xc83e01379a5fbec5fdd1, 0x19d3d70a8d567e388600e, 0x534e2f6e8a4a33155123]]:
 print("".join([chr(32+3*((k>>x)&1))for x in range(79)])) # <anakin@pobox.com>