Copyright and DMCA
Copyright and DMCA 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.
Putty.info publishes original educational text and graphics about PuTTY and SSH. PuTTY software itself is third-party free software distributed by its official project under its own licence—we do not host those binaries here.
Ownership
Unless otherwise credited, written guides, diagrams we create, and site chrome are produced for Putty.info. Quotations from official documentation are limited and attributed with links to primary sources. Trademarks remain the property of their owners and are used for identification.
Copyright complaint notice
If you believe material on putty.info infringes your copyright, send a notice via the contact form with category Copyright concern including:
- Your contact name, mailing address, telephone, and email.
- Identification of the copyrighted work claimed to be infringed.
- The exact URL(s) on putty.info where the material appears.
- A statement that you have a good-faith belief the use is not authorized by the owner, its agent, or the law.
- A statement, under penalty of perjury, that the information is accurate and that you are the owner or authorized to act.
- A physical or electronic signature (typing your full legal name is acceptable for email/form submissions).
This page describes our intake process and is not legal advice. We may remove or restrict access to material while evaluating a complete notice.
Counter-notice
If your material was removed and you believe it was a mistake or misidentification, you may submit a counter-notice with your contact details, identification of the removed material, a good-faith statement of mistake, consent to jurisdiction as applicable, and your signature. We may forward notices to complainants and follow applicable procedures.
Repeat infringement
We may restrict users or contributors who repeatedly infringe copyrights. Putty.info visitor comments, if enabled in future, will be moderated under the same policy.
Software downloads
Copyright complaints about PuTTY binaries should be directed to the official project’s channels when they concern the upstream software. Putty.info will not re-host contested binaries; we link to official locations only.
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 Copyright and DMCA (path /dmca/): 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.