Affiliate Disclosure
Affiliate disclosure
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.
This Affiliate Disclosure explains how Putty.info handles affiliate relationships under applicable endorsement guidelines.
Current status
As of the latest review, Putty.info may participate in affiliate programs in the future for hardware labs, training platforms, or hosting-related tools adjacent to SSH education. When affiliate links are present, we will identify them clearly on this page and near the link where practical. We do not fabricate performance statistics or “sponsored download” funnels for PuTTY itself—PuTTY remains free from its official project.
Rules we follow
- Affiliate relationships will not change safe-download advice: binaries come from official hosts only.
- We will not claim Putty.info is an official partner of the PuTTY project.
- If compensation may influence a non-software product recommendation, we disclose it.
- Educational accuracy outranks commission potential; we remove links that conflict with security guidance.
Examples of what we will not do
- Sell “premium PuTTY” installers.
- Gate essential troubleshooting steps behind paid walls pretending to be the vendor.
- Use fake urgency timers on download pages.
Questions
Questions about commercial relationships: use the contact form. Related pages: Advertising, Editorial policy.
Field notes and runbook extras
Additional operational depth for Affiliate Disclosure (path /affiliate-disclosure/): 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.