nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-01 11:32:48 -05:00
Code Issues Projects Releases Wiki Activity

Add another bug workaround, this one for old OpenSSH (<2.3) servers

Browse Source 
which have a strange idea of what data should be signed in a PK auth
request. This actually got in my way while doing serious things at
work! :-)

[originally from svn r2800]
This commit is contained in:
Simon Tatham
2003-02-04 13:02:51 +00:00
parent b83b9fad77
commit be9718cb13
5 changed files with 74 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/config.but
View File

@ -1,4 +1,4 @@
\versionid $Id: config.but,v 1.53 2003/02/01 02:09:02 jacob Exp $
\versionid $Id: config.but,v 1.54 2003/02/04 13:02:51 simon Exp $
\C{config} Configuring PuTTY
@ -2172,6 +2172,24 @@ workaround, you need to enable it manually.
This is an SSH2-specific bug.
\S{config-ssh-bug-pksessid2} \q{Misuses the session ID in PK auth}
\cfg{winhelp-topic}{ssh.bugs.rsapad2}
Versions below 2.3 of OpenSSH require SSH2 public-key authentication
to be done slightly differently: the data to be signed by the client
contains the session ID formatted in a different way. If public-key
authentication mysteriously does not work but the Event Log (see
\k{using-eventlog}) thinks it has successfully sent a signature, it
might be worth enabling the workaround for this bug to see if it
helps.
If this bug is detected, PuTTY will sign data in the way OpenSSH
expects. If this bug is enabled when talking to a correct server,
SSH2 public-key authentication will fail.
This is an SSH2-specific bug.
\H{config-file} Storing configuration in a file
PuTTY does not currently support storing its configuration in a file