SSH: can't connect to OpenSSH 9 / Ubuntu 22

[Eugeny]

Tabby currently lacks support for rsa-sha2-256/512 private key auth (through node-ssh2).

OpenSSH 8 has deprecated the old ssh-rsa private key auth algorithm in 9.0 since rsa-sha2-256 offers better security with the same key, however Tabby as an SSH client doesn't support it yet.

The error shown in Tabby is All configured authentication methods failed.

As a workaround, you can reenable ssh-rsa auth on the server by adding PubkeyAcceptedAlgorithms +ssh-rsa to your /etc/ssh/sshd_config and reloading the SSH service.

[orangeSi]

My first ssh connect is ok, but got this error when duplicate it. Then I close the whole tabby and restart it, all is ok now~ PS: my system is win10, not linux.

[Uj947nXmRqV2nRaWshKtHzTvckUUpD]

This should be top priority, as it renders Tabby completely unusable for new os systems (latest centos, ubuntu).

[mc36]

the issue is still there... :( i'm running debian sid, that is, the ssh agent is also from ssh9.0p1 right now, and it cannot connect 127.0.0.1:22.. doing ssh localhost connects fine without asking for a thing...

[cayenne17]

the issue is still there... :( i'm running debian sid, that is, the ssh agent is also from ssh9.0p1 right now, and it cannot connect 127.0.0.1:22.. doing ssh localhost connects fine without asking for a thing...

What are the connection conditions? by password or by key? what kind of key ?

what is the error message in the SSH server logs at the time of SSH connection in /var/log/auth.log ?

[Eugeny]

@mc36 are you on v1.0.182?

[Uj947nXmRqV2nRaWshKtHzTvckUUpD]

On build 182, I am able to connect to both Centos 9 and Ubuntu 22. Great work!

[Phil57]

Had to rollback to 181, could not connect anymore.

ecdsa-sha2-nistp256

Ubuntu 20.04.4 LTS OpenSSH 8.2p1-4ubuntu0.5

[mc36]

@mc36 are you on v1.0.182? yesss, the build from 2 days ago...

[mc36]

What are the connection conditions? by password or by key? what kind of key ?

so i try to use the agent to authenticate with my key... (they came from keepassxc, if that matters, but should not) so it's an old 2kbits rsa key... the key, and a lot more, present in ssh-add -L.. moreover, ssh 127.0.0.1 opens fine...

[Aterfax]

X-post.

https://github.com/Eugeny/tabby/issues/5023#issuecomment-1230657424

I think something is unpatched with respect to these new builds when using the Pageant agent. If I supply the private key via the key method in the profile, I can login to endpoints. If I tell it to use Pageant agent I cannot login with the same error as above with v182 and above.

[diego-lima]

I installed release alpha 183 yesterday (tabby-1.0.183-macos-x86_64.pkg) and I am running into this issue.

 SSH  Connecting to diegolm.corp.amazon.com
 SSH  Host key fingerprint:
 SSH   rsa-sha2-256  06/zgi0Ngu18kJEClzJDu87p+uORbKDVF2OyklIk62s= 
 SSH  Loading private key: file:///Users/diegolm/.ssh/id_rsa
 X  All configured authentication methods failed
 SSH   X  Remote rejected opening a shell channel: Error: Not connected

There's also a log on devtools stating Server does not support auth method hostbased

I will just run ssh <hostname> in a regular tab as always

[tennox]

Same here

[Issues-translate-bot]

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

---

Same here

[Aterfax]

Still having this problem under Ubuntu 22.04 with Tabby 1.0.186 - is this related to issues in the ssh2 package?

https://github.com/mscdex/ssh2/issues/989

Edit: FYI for people wanting a quick(ish) resolution. Just make a new ed25519 SSH key pair, update your endpoints and user accounts authorized_keys with it and Tabby should resume working.