Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Administered by:

Server stats:

268
active users

en.osm.town: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#putty

0 posts0 participants0 posts today
Public
Simon Tatham

Always nice when software developers have thought of the thing you wanted already.

When #git on my laptop wants to talk to my machine at home (usually to continue work on something I left half-finished, append another commit or two, and push it back to my home checkout), it has to use #PuTTY rather than OpenSSH, because only my PuTTY configuration knows how to find its way to that machine. So I have to set either GIT_SSH or core.sshCommand to "plink". Ideally the latter, and only in the context of that one checkout.

What this _really_ needs, I thought, is an option to 'git clone' that will set an arbitrary 'git config' option early enough to affect the actual cloning operation, and then leave it set in the resulting checkout. That'd be perfect. I wonder if the git developers have thought to provide one?

And they have! #TIL 'git clone -c key=value'.

git clone -c core.sshCommand=plink my-home-machine:src/half-finished-thing

Public
Simon Tatham

We've released #PuTTY version 0.83.

This release is mostly full of bug fixes following up the new development in 0.82. Most significantly, 'psftp -b' was completely broken, and now works again. Also various assertion failures, crashes and hangs. On the Unix side, we've fixed an intermittent bug making the keys on the small keypad above the arrows (Home, End, Ins, Del etc) not work in the terminal.

We've also extended our #quantumsafe cryptography support, by supporting #MLKEM as a key exchange option, in addition to NTRU Prime which we already had.

chiark.greenend.org.uk/~sgtath

www.chiark.greenend.org.ukPuTTY: a free SSH and Telnet client
Public
Lanie Carmelo

@1password hoping you can help here. I'm using #1Password and #OpenSSH in #WindowsTerminal here on #Windows11 to connect to my #RaspberryPi. I need an easier way to work with files, though, so I'm trying to set up #WinSCP. I've exported my key from 1Password in both formats available. I noticed it didn't have a file extension so added .pem to the name. No matter what I do, WinSCP won't take the key. Neither would #PuTTY when I tried it. Do you have any suggestions on how to resolve this? Anyone else who thinks they might be able to help is welcome to reply too.
#Linux #Windows #SSH #RaspberryPiOS #Tech #Technology

Public
Simon Tatham

Pre-release builds of #PuTTY 0.83 are now available.

This is mostly a bug-fix release. 0.82 went out in a bit of a hurry, and users reported half a dozen bugs quite quickly, most notably that PSFTP forgot how to handle the -b option. Those are now all fixed.

Also new: support for a 2nd post-quantum key agreement scheme (ML-KEM), and improved support for Unicode filenames on Windows.

Please test! If there are still bugs, we'd like to fix them _before_ releasing 0.83.

chiark.greenend.org.uk/~sgtath

www.chiark.greenend.org.ukDownload PuTTY: pre-releases of 0.83
Public *
Royce Williams

PuTTY for Debian bookworm is at 0.78; 0.82 was released today and has significant Unicode rework that is relevant to my interests. I have no idea why Debian's PuTTY is so far behind. Compiling from source works with zero errors, building all the binaries (pageant, etc.) ... but not putty itself. Checking out previous releases from git, they also skip putty itself. 🤷

Am I missing something obvious or well known?

#PuTTY#Debian
Public
Simon Tatham

We've released #PuTTY version 0.82.

The biggest change is improved Unicode support. Usernames and passwords read from the terminal or the Windows console now support full Unicode, so that you can use characters outside the Windows system code page, or the character set configured in PuTTY. The same is true for usernames and file names provided via the PuTTY tools' command line and via the GUI (but unfortunately not yet if you save and reload a session).

Public
Simon Tatham

I've just renewed the #Authenticode certificate I use to sign #PuTTY.

Now #Windows #Defender gives me dire warnings about my own nightly builds. Apparently it thinks the new cert belongs to some previously unknown SW publisher, who might be a malware source for all it knows.

Is there any way to reassure it? E.g. the old cert hasn't expired yet, so I could use each one to cross-sign a declaration that the other one belongs to the same person.

Is there a standard procedure for this?

Public
Amin Girasol

I'm really getting much more of a chuckle from the puzzles thrown up by trying to use a #VintagePC on a modern network than I ever expected!

Modern #puTTY binaries won't run on #WindowsNT4; ancient binaries from January 2000 are available and will run, but can't connect to a modern #SSH server. Most effective for file transfer is a combination of #telnet specially installed on my daily driver #Linux machine and python3 -m http.server.

Netscape 4.7 works nicely with the Python HTTP server, and the telnet client that comes with Windows NT4 supports VT100 so on opening a shell on my Linux machine, I find the w3m command line web browser is just about usable - good enough to download ancient binaries and installers onto the Linux machine that can be served via Python's HTTP server.

I've also given #wrp, the Web Rendering Proxy, a spin; it's surprisingly effective. Runs on a Linux machine on the network and serves pages as GIFs with clickable image maps.

github.com/tenox7/wrp

A photo of the LCD panel in my Thinkpad 760CD, showing a mostly occluded Netscape 4.7 window, a `cmd` session and the Windows NT4 graphical Telnet client running `w3m`.
Public
Josh Bressers

I booted windows and installed #PuTTY last night to see how common an ECDSA-512 key could be (and I bet loads of people here don't run windows or PuTTY, so here's some details)

PuTTY doesn't generate ssh keys, you have to use a different tool that comes with PuTTY called PuTTYgen

The key generated by default is a 2048 bit RSA key

If I pick ECDSA as the key type, it defaults to a 256 bit key (it's not hard to pick a 512 bit key, but it's not the default)

I have a suspicion the number of PuTTY users with 512 bit ECDSA keys is going to be pretty small, which is excellent news.

Public
Benjamin Carr, Ph.D. 👨🏻‍💻🧬

#PuTTY #SSH client flaw allows recovery of #cryptographic #privatekeys
The vulnerability (CVE-2024-31497) was discovered by Fabian Bäumer and Marcus Brinkmann of the Ruhr University Bochum and is caused by how PuTTY generates #ECDSA nonces (temporary unique cryptographic numbers) for the NIST P-521 curve used for SSH authentication. The main repercussion of recovering the private key is that it allows unauthorized access to SSH servers or sign commits as the developer.
bleepingcomputer.com/news/secu

ExploreLive feeds
About