Download Putty Version 0.74 !NEW!
Karla Ganger
This page containsdownload links forPuTTY release 0.74.0.74, released on 2020-06-27, is not the latest release.See theLatest Release pagefor the most up-to-date release (currently 0.80).Past releases of PuTTY are versions we thought were reasonably likelyto work well, at the time they were released. However, later releaseswill almost always have fixed bugs and/or added new features. If youhave a problem with this release, please trythe latest release,to see if the problem has already been fixed.SECURITY WARNINGThis release has known security vulnerabilities.Consider using a later release instead, such as the latest version, 0.80.
These features are planned for the next full release (and shouldtherefore be available in the development snapshots, unless they'renot updating, which happens sometimes):-->For features planned for the next full release (and already available inthe development snapshots), see the wishlist page.These features arenew in0.80(released 2023-12-18):
- Security fix: support for OpenSSH's new kex-strictprotocol modification, addressing a vulnerability in so...@openssh.com cipher and MAC modes, in particularChaCha20+Poly1305.
- Bug fix: the MSI-installed version of putty.exe cannow find its help file again.
- Bug fix: a server sending non-displaying terminal escape sequencessuch as ESC[0m now no longer resets the scrollback to thebottom of the window.
- Windows installer scope is back to the normal 'per machine'setting, reverting 0.78's security workaround.Note: this means that installing the 0.79 or later Windowsinstaller will not automatically uninstall 0.78, if 0.78 wasinstalled using its default 'per user' scope. In that situation werecommend uninstalling 0.78 first, if possible. If both end upinstalled, uninstalling both and then re-installing the new versionwill fix things up.
certificates were generated on the target server using ssh-keygen and the private key was converted to .ppk format locally using PuTTYgen
certificates were created locally on a Windows machine using PuTTYgen
In both scenarios, when a newer version of PuTTYgen was used to convert the key (0.74, 0.75) CCS would not connect to the target asset saying:
The short answer for future viewers of this question is that PuTTY 0.71 at least and possibly other versions require adding -P 22 to the command line even in the default case, so it's necessary to set SSH Port to Use Specified Port and 22. Otherwise, Wing does not add a -P to the command line, which is done because it's possible to configure the port outside of Wing also, through putty.exe or in .ssh/config if using OpenSSH. The UI will be changed in Wing 7.2.8.1+ to clarify that default doesn't necessarily mean port 22.
If you bring up putty.exe, does it have a saved entry for the particular remote host? That can be used to change the port number used to something other than port 22, and I think the above dialog in that case is misleading because it assumes the ssh command line system will use port 22 by default. In fact that's also true for OpenSSH, where a different port can be set in the config file. We'll try to clarify that in any case.
Could you please send in a bug report from Wing's Help menu right after reproducing the problem? Please include the error log, which will contain the putty commands we've run during the install including any output and errors.