Cookie Policy
Cookie Policy
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 Cookie Policy explains how Putty.info uses cookies and similar technologies. It should be read with our Privacy Policy.
Essential cookies
We use essential cookies and similar storage to operate security controls such as CSRF protection, maintain administrative login sessions, and remember necessary consent choices where applicable. These are required for core site functions and are not used to advertise products to you.
Analytics
The keyword-sites platform may set a network session or analytics identifier to measure aggregate traffic (which guides are read, approximate geography, and technical success rates). We use this to prioritize editorial work—for example expanding thin troubleshooting pages—not to sell individual profiles.
Advertising cookies
When advertising is enabled, third parties such as Google may set cookies or use advertising identifiers to serve and measure ads according to their policies and any consent choices you make. You can learn more in our Advertising Disclosure and in your browser’s cookie controls. We instruct that ads must remain clearly labeled and must not mimic download CTAs.
Managing cookies
Most browsers let you block or delete cookies. Blocking essential cookies may break admin login or form submission. Where a consent banner or preference center is presented by the hosting stack, use it to adjust non-essential categories. Enterprise browsers may enforce additional policies beyond your personal settings.
Updates
We may update this Cookie Policy as technologies change. The reviewed date on this page reflects the latest editorial pass.
Field notes and runbook extras
Additional operational depth for Cookie Policy (path /cookie-policy/): 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.