Closed drok closed 1 year ago
It would be helpful if you could set up a docker container with a server that triggers the error to make it easily reproducible, then we can have a look. See https://github.com/dlech/SshAgentLib/tree/master/docker for some examples.
Hi,
thank you for creating and maintaining Kee Agent :)
I think I experience a issue similar, if not the same.
After some time the agent connection for Windows ssh agent breaks:
ssh-add -l
hangs tooThat putty still works suggests that this is not a server problem.
I think I experience this since quite some time, I only recently discovered that this is not Windows↔WSL port mappings breaking down but this issue.
This is a log with working agent:
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
debug1: Will attempt key: --%<-- RSA SHA256:--%<-- agent
This where it hangs:
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
# after some time I abort with CTRL-C
C:\Users\...>
Versions:
KeePass | 2.53 (64bit) |
KeeAgent | 0.13.4.0 |
Windows | Windows 10 Enterprise, 21H2 19044.2486 |
Windows SSH | OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2 |
If I find/take the time to set up a debugging environment I'll report back.
closing as duplicate of #362
After many years of using KeeAgent various versions, I attempted upgrading from 0.12.1 to 0.13.3 (latest at this time) in order to gain the ability to use the Putty v3 ppk key file format, which per the Changelog are supported since 0.13.1
This upgrade broke my previously working configuration. Reverting to 0.12.1 restores the working state. Below are the output of "
ssh -vvv -T 10.6.9.59 echo success
" from the client towards the server which is running "/usr/sbin/sshd -ddd
" ; I have inserted into each log some notes prefixed with '#' that describe what I see. First the client side and server side logs using KeeAgent 0.13.3 are included, and below, the same test after reverting to 0.12.1:Client side, KeeAgent 0.13.3 (repro hung connection):
Server side (repro hung connection)
Reproducing working configuration
When KeeAgent 0.12.1 is used on the client side, and no other changes, the command "ssh -vvv -T 10.6.9.59 echo success" runs normally on the client, authenticating as expected and returning without user intervention. Here are the client-side and server-side logs, respectively, showing a normal handshake with KeeAgent 0.12.1:
Client side log (repro normal handshake):
Server-side log (repro normal handshake)
Thank you for this godsend extension to Keepass, I have been relying on it for many years of flawless daily operation, without giving it much thought. "It just works" and I love it. I hope the good track record can be restored.