&
SEO LEO
Home
|
Licence
|
FAQ
|
Docs
|
Download
|
Keys
|
Links
Mirrors
|
Updates
|
Feedback
|
Changes
|
Wishlist
|
Team
Here are the PuTTY files themselves:
LEGAL WARNING: Use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is outlawed. We believe it is legal to use PuTTY, PSCP, PSFTP and Plink in England and Wales and in many other countries, but we are not lawyers, and so if in doubt you should seek legal advice before downloading it. You may find useful information at cryptolaw.org, which collects information on cryptography laws in many countries, but we can't vouch for its correctness.
Use of the Telnet-only binary (PuTTYtel) is unrestricted by any cryptography laws.
There are cryptographic signatures available for all the files we offer below. We also supply cryptographically signed lists of checksums. To download our public keys and find out more about our signature policy, visit the Keys page. If you need a Windows program to compute MD5 checksums, you could try this one at pc-tools.net. (This MD5 program is also cryptographically signed by its author.)
This will generally be a version we think is reasonably likely to work well. If you have a problem with the release version, it might be worth trying out the latest development snapshot (below) to see if we've already fixed the bug, before reporting it.
This will be built every day, automatically, from the current development code - in whatever state it's currently in. If you need a fix for a particularly inconvenient bug, you may well be able to find a fixed PuTTY here well before the fix makes it into the release version above. On the other hand, these snapshots might sometimes be unstable.
(The filename of the development snapshot installer contains the snapshot date, so it will change every night.)
This is the source code for all of the PuTTY utilities.
For convenience, we provide several versions of the source code, for different platforms. The actual content does not differ substantially between Windows and Unix archives; the differences are mostly in formatting (filenames, line endings, etc).
If you want to do any PuTTY development work, we strongly recommend starting with development snapshot code. We frequently make large changes to the code after major releases, so code based on the current release will be hard for us to use.
These .tar.gz source archives should build the latest
release version, and latest development snapshot, of PuTTY for Unix.
To build the release
source, you will need to unpack one of these archives, change into the
"unix" subdirectory, and type "make -f
Makefile.gtk". To build the development snapshot source, you
can just do the standard thing of ./configure &&
make. See the file "README" for more information.
(The filename of the development snapshot source archive contains the snapshot date, so it will change every night.)
See the file "README" for more information on building
PuTTY from source.
git
If you want to keep track of the PuTTY development right up to the
minute, or view the change logs for each of the files in the source
base, you can access the PuTTY master git repository
directly, using a command such as
git clone https://git.tartarus.org/simon/putty.gitAlternatively, you can browse the git repository on the web.