Differences From Artifact [b1462acb61]:
- File ssh.c — part of check-in [5ecfcce6b6] at 2005-11-13 10:06:41 on branch trunk — r6437 broke the case where Pageant is running but contains no SSH-2 keys that the SSH-2 server is happy with. Fixed, and since I'm here, fix `pubkeyfile-and-pageant' as well (for SSH-1 and SSH-2). Also, in SSH-2, we now reexamine "methods that can continue" for every Pageant key offer, which is technically more correct although it seems unlikely that it was causing any real problems. (It's not entirely pretty, but neither was the old code. We could probably do with some sort of abstraction for public/private keys to avoid carting lots of fiddly bits of data around.) (user: jacob size: 260466)
To Artifact [5eb30a6331]:
- File ssh.c — part of check-in [0cf3aea3e9] at 2005-12-07 12:01:40 on branch trunk — Apparently some SSH servers object to our claiming port-forwarded connections to be from IP "client-side-connection". Claiming "0.0.0.0" instead seems to work. Spotted by Brant Thomsen. (user: jacob size: 260605)
| ︙ | |||
8686 8687 8688 8689 8690 8691 8692 8693 | 8686 8687 8688 8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 | + + + - + | ssh2_pkt_addstring(pktout, hostname); ssh2_pkt_adduint32(pktout, port); /* * We make up values for the originator data; partly it's * too much hassle to keep track, and partly I'm not * convinced the server should be told details like that * about my local network configuration. * The "originator IP address" is syntactically a numeric * IP address, and some servers (e.g., Tectia) get upset * if it doesn't match this syntax. */ |
| ︙ |