PuTTY bug plink-hostname

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

summary: Plink using wrong hostname when one is saved in Default Settings
class: bug: This is clearly an actual problem we want fixed.
difficulty: fun: Just needs tuits, and not many of them.
priority: high: This should be fixed in the next release.
present-in: 0.60
fixed-in: r8651 d992932e1eb1515d4674ab806730d13b4bf9223c 2009-09-15 (0.61)

Since 'defaults-launchable' was fixed, it's been possible to save a hostname in Default Settings.

However, Plink did not cope gracefully with that possibility -- it was not possible to override that hostname on the command line. Attempts at doing so would be treated as part of the remote command, but this typically wouldn't be obvious as the connection wouldn't get that far.

The most common symptom of this is output like this:

C:\>plink myhost.example.com
Unable to open connection:
Host does not exist
where a PuTTY connection to myhost.example.com works fine. Upon adding the -v option you might get:
C:\>plink -v myhost.example.com
Looking up host "otherhost.example.com"
Unable to open connection:
Host does not exist
which "huh?" behaviour is explained by otherhost.example.com being in "Default Settings".


If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2016-12-27 11:40:21 +0000)