Release Notes for PuTTY beta 0.71

If you access this software from the Start Menu, with UofR Software Distribution\Installers, then installation is automatic. If you downloaded the installer from the UofR web site, double click on the Putty7.1Installer.exe to start the install.

Software Description

PuTTY is a free implementation of Telnet and SSH for Win32 and Unix platforms, along with an xterm terminal emulator. It is written and maintained primarily by Simon Tatham. The PuTTY files included in the installation are PuTTY (the Telnet and SSH client itself) and PuTTYgen (an RSA and DSA key generation utility). Some features of PuTTY are:

  • The storing of hosts and preferences for later use.
  • Control over the SSH encryption key and protocol version.
  • Command-line SCP and SFTP clients, called "pscp" and "psftp" respectively.
  • Control over port forwarding with SSH, including built-in handling of X11 forwarding.
  • Emulates most xterm, VT102 control sequences, as well as much of ECMA-48 terminal emulation.
  • IPv6 support.
  • Support 3DES, AES, Arcfour, Blowfish, DES.
  • Public-key authentication support.
  • Support for local serial port connections.


  • A IBM compatible computer with Pentium processor or better
  • Microsoft Windows Vista/Windows 7/8/10.
  • 16Mb of RAM(32Mb of RAM highly recommended)
  • 2Mb of free disk space

Licensing Terms

The PuTTY executables and source code are distributed under the MIT licence, which is similar in effect to the BSD licence. (This licence is Open Source certified and complies with the Debian Free Software Guidelines.)

Additional Documentation

  • After installation an icon will be present in the Putty group of the Start Menu, as well as in the path C:\Program Files\Putty
  • Starting a Session: Single clicking the Start Menu icon will launch the program and display a screen of default host sessions you may click on, or in the Host Name box, enter the Internet host name of the server you want to connect to. You should have been told this by the provider of your login account. Now select a login protocol to use, from the Connection type buttons. For a login session, you should select Raw, Telnet, Rlogin or SSH. When you change the selected protocol, the number in the Port box will change. This is normal: it happens because the various login services are usually provided on different network ports by the server machine. Most servers will use the standard port numbers, so you will not need to change the port setting. If your server provides login services on a non-standard port, your system administrator should have told you which one. (Once you have filled in the Host Name, Protocol, and possibly Port settings, you are ready to connect. Press the Open button at the bottom of the dialog box, and PuTTY will begin trying to connect you to the server.
  • Logging in: After you have connected, and perhaps verified the server's host key, you will be asked to log in, probably using a username and a password. Your system administrator should have provided you with these. Enter the username and the password, and the server should grant you access and begin your session. If you have mistyped your password, most servers will give you several chances to get it right. If you are using SSH, be careful not to type your username wrongly, because you will not have a chance to correct it after you press Return; many SSH servers do not permit you to make two login attempts using different usernames. If you type your username wrongly, you must close PuTTY and start again. If your password is refused but you are sure you have typed it correctly, check that Caps Lock is not enabled. Many login servers, particularly Unix computers, treat upper case and lower case as different when checking your password; so if Caps Lock is on, your password will probably be refused.
  • After Logging in: After you log in to the server, what happens next is up to the server! Most servers will print some sort of login message and then present a prompt, at which you can type commands which the server will carry out. Some servers will offer you on-line help; others might not. If you are in doubt about what to do next, consult your system administrator.
  • Logging out: When you have finished your session, you should log out by typing the server's own logout command. This might vary between servers; if in doubt, try logout or exit, or consult a manual or your system administrator. When the server processes your logout command, the PuTTY window should close itself automatically. You can close a PuTTY session using the Close button in the window border, but this might confuse the server - a bit like hanging up a telephone unexpectedly in the middle of a conversation. We recommend you do not do this unless the server has stopped responding to you and you cannot close the window any other way.
  • For additional documentation you can visit the Putty Web Site.

Known Problems

Please report problems to Be advised that PuTTY is considered a stable beta. If you experience problems with this software please make a note of any error messages and the conditions under which you experienced the problems prior to reporting the problems to the Computing Services helpdesk.

Changes from Previous Version

  • A complete list of changes from version to version can be viewed here.
  • August 04/2009: was added as a terminal type.
  • Installer was changed so that if a terminal type was present in the registry it would not be overwritten.
  • Default connection was changed to send keep-alive packet every 120 seconds.
  • August 27/2009: The terminal type was changed to match the setup requested here.
  • May 14/2013: Change for Putty version 6.2
  • January 10/2014: Change for Putty version 6.3
  • December 13/2016: Remove XP, add Windows 10
  • December 5/2018: Change for Putty version 6.8
  • March 25/2019: Change for Putty version 7.1