Resources
Resource directory
Independent resource: Putty.info is an independent educational website about PuTTY and SSH. It is not affiliated with, operated by, sponsored by, or endorsed by the official PuTTY project or Simon Tatham. We do not host PuTTY binaries.
Use this page as a map to first-party Putty.info hubs and to primary official PuTTY project resources. Prefer primary sources whenever you need authoritative release or licence text.
Official PuTTY project links
- Official latest download page
- Official documentation (HTML)
- the.earth.li PuTTY mirror tree
- Project home and licence pages linked from the official site navigation
Putty.info mirrors none of these binaries. Our /go/official-download/ path exists to send browsers to allowlisted official destinations after checks.
Putty.info hubs
Site policies
How to use these resources
Start with download provenance, then learn sessions and host keys, then keys and file transfer, then tunnels. When errors appear, match the exact dialog text to an error guide before changing servers. Always re-check UI labels against your installed version using the official manual if something looks different.
Primary references: official latest download page, official PuTTY documentation, and this site's official-download redirect plus safe download guide and latest version notes.
Field notes and runbook extras
Additional operational depth for Resources (path /resources/): treat every change to authentication, forwarding, or host-key storage as a reversible change under change control. Record the PuTTY version string from Help → About, the Windows build, and whether Pageant was running. Those three facts explain a surprising fraction of “it works on my laptop” discrepancies.
When documenting the procedure for teammates, include: the saved session name, Host Name and Port from the Session panel, whether Connection type is SSH, the username, whether a PPK path is set under Connection → SSH → Auth, and whether agent forwarding is enabled. Explicitly state that Putty.info is an independent educational site and that binaries must be obtained from the official project download page. Link readers to safe download guidance, host key verification, and the official manual so they can cross-check labels that differ slightly across releases.
If you still need more diagnostics after following the sections above, reproduce the issue with logging enabled under Session → Logging to a local file you control, scrub secrets from the transcript, and compare against server auth logs for the same UTC timestamp. Avoid third-party “PuTTY fix” utilities. Prefer updating to the current stable release from official hosts, re-importing a known-good saved session, and testing from a second network path before declaring the workstation broken.
- Keep private keys passphrase-protected and backed up offline according to your organization's secret-handling policy.
- Prefer named saved sessions over ad-hoc connections for anything beyond a one-off debug.
- Disable unused tunnels and agent forwarding by default; enable them per session only when required.
- Schedule periodic key rotation and remove stale authorized_keys entries during access reviews.
- Teach new operators the difference between connection errors and authentication errors before giving them production bastion access.