Hello Jacob,
I tested the patch from your previous message with putty 0.82-1
(currently available in Debian Unstable and Debian Testing), which I
found to be affected by the same bug as the previous version 0.81-3.
It works :-)
For those interested, these are the commands I used to patch the source
and rebuild the package locally (note: I saved Jacob's patch locally as
a text file named "putty.patch") in Debian Testing:
$ sudo apt install packaging-dev
$ apt source putty
$ sudo apt build-dep putty
$ cd putty-0.82/
$ quilt import ../putty.patch
$ quilt push
$ quilt pop -a
$ dch -i "test build"
$ dpkg-buildpackage -b
Wait for verification from other people, many thanks to Jacob.
On 04/12/2024 19:09, Jacob Nevins wrote:
UBSAN has found me a reliance on uninitialised data / undefined
behaviour that affects these keys specifically. Fixed here:
https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=6a88b294276b9c24584efa18b9a37f437fa46712
This may have some bearing on the matter.
If someone (who can reproduce this behaviour with a freshly locally
compiled version of PuTTY/pterm) can try applying this patch (attached
for convenience) and see if it helps, that might be helpful.
(If this is it, it's been latent since 0.78; I guess we just started
getting unlucky with the toolchain recently or something.)
