PuTTY Links

Home | Licence | FAQ | Docs | Download | Keys | Links
Mirrors | Updates | Feedback | Changes | Wishlist | Team

Related software

Several pieces of third-party software incorporate parts of the PuTTY code, or augment PuTTY in other ways, to provide facilities not available from PuTTY itself. We list some of them here, with no recommendation implied. We have no control over this code, so we can't vouch for either its quality or its security.

Software based on PuTTY's code

These projects include actual code from some version of PuTTY.

• NettleSSH, an SSH client for RISC OS
• SSHProxy and pscp for RISC OS
• PuTTY for Nokia 9200 Communicator Series
• pssh, a Palm OS SSH-2 client that uses some PuTTY terminal code
• WinSCP, a GUI SFTP and SCP client
• FileZilla, a GUI file transfer client with SFTP support from PuTTY
• SSHDOS, SSH, SCP, SFTP and Telnet client for MS-DOS
• PuTTY with ISO-2022 support, and other things Japanese
• PuTTY DBCS Patched, with a Chinese feel
• Arabeyes PuTTY, a project to add Arabic support to PuTTY (see also wishlist entry)
• transputty, PuTTY with fake transparency
• PowTTY, a MUD client
• PuTTY IPv6 build
• PuTTYcyg, to use PuTTY as a terminal for Cygwin
• PuTTY with GSSAPI/Kerberos support
• TortoiseCVS and TortoiseSVN, Windows Explorer frontends to CVS and Subversion respectively, use a modified Plink for SSH transport.
• Polish localised version of PuTTY (no source)
• PocketPuTTY, a port of 0.53b for Windows Mobile 2003 (no source yet)
• IVT, a VT220 emulator which uses some PuTTY code (no source)
• Safe Passage, an alternative to PuTTY's dynamic port forwarding which doesn't require SOCKS support in your client applications (it seems to install itself somehow at the Windows networking level). Based on the PuTTY code. Commercial, but cheap.

Other related software

• Secure iXplorer GPL, a GUI SFTP client
• CallingHome, for maintaining long-running SSH tunnels using PuTTY.
• KPuTTY and GPuTTY, PuTTY-lookalike frontends for Unix
• PuTTY Magic provides borderlessness, transparency, and alphablending in PuTTY.
• QuickPutty, for quickly launching PuTTY saved sessions
• Secure iXplorer Pro, a GUI SFTP client (commercial, no source)

Specifications implemented by PuTTY

PuTTY attempts to conform to many specifications. These include:

SSH-2 specifications

• IETF Secure Shell working group - we claim to implement the following:
  • Core: architecture, transport, userauth, connect, assignednumbers
  • dh-group-exchange
  • auth-kbdinteract
  • break
  • fingerprint
  • publickeyfile
  • filexfer

SSH-1 specification

• The SSH (Secure Shell) Remote Login Protocol
• We don't know of a reference for the SCP protocol (which is basically BSD rcp).

Telnet specifications

• RFC 854: TELNET Protocol Specification
• RFC 855: TELNET Option Specifications
• RFC 856: TELNET Binary Transmission
• RFC 857: TELNET Echo Option
• RFC 858: TELNET Suppress Go Ahead Option
• RFC 1073: Telnet Window Size Option
• RFC 1079: Telnet Terminal Speed Option
• RFC 1091: Telnet Terminal-Type Option
• RFC 1408: Telnet Environment Option
• RFC 1571: Telnet Environment Option Interoperability Issues
• RFC 1572: Telnet Environment Option

Rlogin specification

• RFC 1282: BSD Rlogin

HTTP specifications

• RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
• RFC 2617: HTTP Authentication: Basic and Digest Access Authentication
• RFC 2817: Upgrading to TLS Within HTTP/1.1 (HTTP CONNECT)

SOCKS specifications

• SOCKS: A protocol for TCP proxy across firewalls (SOCKS 4)
• SOCKS 4A: A Simple Extension to SOCKS 4 Protocol
• RFC 1928: SOCKS Protocol Version 5
• RFC 1929: Username/Password Authentication for SOCKS V5
• Challenge-Handshake Authentication Protocol for SOCKS V5 is only available as an expired Internet-Draft.

Terminal specifications

• ECMA-35: Character Code Structure and Extension Techniques (equivalent to ISO 2022)
• ECMA-48: Control Functions for Coded Character Sets (equivalent to ISO 6429)

Zlib compressed data format

• RFC 1950: ZLIB Compressed Data Format Specification (this is mostly just wrapping and red tape)
• RFC 1951: DEFLATE Compressed Data Format Specification (this contains the details of the actual compressed data)

Cryptographic algorithms

• NIST FIPS 46-3 defines the DES block cipher.
• Bruce Schneier's page on the Blowfish block cipher.
• NIST FIPS 197 defines the AES block cipher.
• RFC 1321 defines the MD5 hash function.
• NIST FIPS 180-2 defines secure hash functions SHA-1 and SHA-512.
• RFC 2104 defines HMAC, a generic wrapper mechanism that converts a hash function such as MD5 or SHA-1 into a secure MAC.
• NIST FIPS 186-2 defines the digital signature algorithm DSA (also known as DSS).
• RFC 3447 (PKCS #1) defines the basic RSA encryption algorithm as well as a specific padding scheme to turn it into a set of well defined operations on byte strings.
• The precise form of Diffie-Hellman key exchange used in SSH-2 is defined in the SSH-2 transport layer specification: see the SSH-2 section above.