About Putty.info
About Putty.info
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.
Putty.info is an independent educational website that helps people download PuTTY safely (by linking to official hosts), learn SSH client workflows on Windows, manage keys with PuTTYgen and Pageant, transfer files with PSCP/PSFTP, and troubleshoot common errors.
What we are not
- Not the official PuTTY project and not affiliated with it.
- Not a host of PuTTY binaries or modified “PuTTY Pro” installers.
- Not a managed service provider or paid incident-response firm by default.
- Not a marketplace for SSH accounts or proxies.
What we offer
Original guides, a glossary, security explainers, version orientation pages fed by monitored official sources, and interactive helpers that refuse private-key paste. Legal pages document privacy, cookies, terms, copyright intake, accessibility, and editorial standards.
Funding
The site may use labeled advertising or future affiliate links as disclosed on their respective pages. Funding does not purchase technical conclusions about safety.
Contact
Use the on-site contact form for corrections, accessibility barriers, privacy questions, and copyright concerns. Do not send secrets. For upstream PuTTY bugs and feature requests, use the official project’s communication channels listed on its site.
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 About Putty.info (path /about/): 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.