Pageant connexion error

[Figoware]

Describe the problem:
Since 1.0.218, unable to connect using Pageant:

 SSH  Connecting to XXXX
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:XXXXX 
 SSH   !  Failed to authenticate using agent: Error: Key(IO(Custom { kind: UnexpectedEof, error: "early eof" }))

 SSH  Connecting to XXXX
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:XXXXX
 SSH   !  Failed to authenticate using agent: Error: Key(AgentFailure)
 X  Authentication rejected

To Reproduce:
Open SSH profile with agent authentification
Using Pageant 0.82

[atlanticfirst]

same issue

[MonkeyHarris]

I'm having the same issue. The Tabby 1.0.219 changelog looked promising ("Fixed SSH agent auth") but unfortunately it's still happening with that. Going back to 1.0.215 fixes the problem.

[Draghmar]

Using KeeAgent from KeePass results in the same issue. Version 1.0.215 works fine.

[rafaelorafaelo]

same issue. 1.0.215 works fine.

[rushowr]

Having the same issue, tabby 1.0.219, putty suite 0.82.

[Figoware]

Just tested with 1.0.220, look promsing too! ("fixed agent auth")... But still not working sadly. Back to 1.0.215!

 SSH  Connecting to XXX
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:XXXX
 X  Authentication rejected

[Draghmar]

Yup, can confirm the same thing on .220 as @Figoware has. The previous error message is gone but still it doesn't auth.

[Figoware]

.221 test: back to .218 results:

 SSH  Connecting to XXX
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:XXX
 SSH   !  Failed to authenticate using agent: Error: Key(AgentFailure)

[rcasta74]

I confirm that the issue is not solved with v1.0.221

Similar to #10248, if I start Tabby from PowerShell it works instead.

Further, selecting authorization method auto, after that it fails with agent, it doesn't work anymore even inserting the password (it gets stuck to connecting message).

I have tried to run in debug mode as described in Capturing a debug log from the SSH backend, but I don' t get any DEBUG message (maybe some company restrictions are preventing it), anyway, since with PowerShell it works, it wouldn't be of any help.