Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSH connection fires the error "Authentication failed" with version 1.0.222. Works with 1.0.221 #10347

Open
jack-y opened this issue Mar 6, 2025 · 32 comments

Comments

@jack-y
Copy link

jack-y commented Mar 6, 2025

Version: 1.0.222
Platform: Linux x64 6.8.0-55-generic
Plugins: quick-cmds
Frontend: xterm-webgl

SSH connection : port 22, with username and authentication with private key file.
The connection is established with v1.0.221
The connection fails with v1.0.222

@adam-kulagowski
Copy link

I can confirm. Fresh installation, no plugins. Tabby detects id_rsa private key file, tries to use it and fails. Same SSH session using CLI ssh works from tabby bash terminal. Rollback to 1.0.221 fixes the issue.

@hnajib-sym
Copy link

Same here , had to rollback , selected all Ciphers , key exchange , HMAC & host key.

@tomazz75
Copy link

tomazz75 commented Mar 6, 2025

Same error, I see this in server logs "sshd[2141525]: userauth_pubkey: signature algorithm ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]". So I can fix it on server side, but it was working fine with previous version.

@breakstring
Copy link

Same issue here.

@Statrue
Copy link

Statrue commented Mar 6, 2025

The same problem and a similar error: signature algorithm ssh-rsa not in PubkeyAcceptedAlgorithms

@eroself
Copy link

eroself commented Mar 6, 2025

Same issue, rolled back

@toffelwurst
Copy link

Same for me on 1.0.222, looks like 1.0.222 always presents the deprecated ssh-rsa (sha1) hash to the server for authentication, no matter what ciphers you check/uncheck in settings.

I supsect commit d1c1b48 to be the culprit

Rollback to 1.0.221 fixed it. 1.0.221 uses sha256 hash for authentication.

@huxiang
Copy link

huxiang commented Mar 7, 2025

Same issue here.

@CryptoSiD
Copy link

Same issue.

@GyuHo123
Copy link

GyuHo123 commented Mar 7, 2025

Same for me on 1.0.222. Rollback to 1.0.221 fixed it.

@SingKS8
Copy link

SingKS8 commented Mar 7, 2025

Same issue here, after upgrading to 1.0.222

@kay-zhu
Copy link

kay-zhu commented Mar 7, 2025

Same issue here, after upgrading to 1.0.222

@aquiveal
Copy link

aquiveal commented Mar 7, 2025

I had the same issue and was going crazy trying to figure out what was wrong.

@HopeAndWish
Copy link

Same issue.

@ikkira
Copy link

ikkira commented Mar 8, 2025

Same issue.

1 similar comment
@imotfnir
Copy link

imotfnir commented Mar 8, 2025

Same issue.

@hugalafutro
Copy link

Any workaround other than downgrade? It's a massive pita I just upgraded tabby on like 8 machines 😆

@Asthaknes
Copy link

You can change your RSA key to an ECDSA key and it will work... ;-)

@Eugeny
Copy link
Owner

Eugeny commented Mar 9, 2025

Please try the latest nightly build, it should be fixed there.

@CryptoSiD
Copy link

Please try the latest nightly build, it should be fixed there.

I might sound dumb but, where can we get the nightly build?

@Eugeny
Copy link
Owner

Eugeny commented Mar 9, 2025

@hugalafutro
Copy link

Just tried nightly, still the same

 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:1TJuuyMDGWibVO19FUGyNDUXMCa4p3H8Q1njHQWLDCI 
 SSH  Trying private key: file://O:\Nextcloud\sys\ssh\docker-vm\id_rsa
 X  Authentication rejected

on win11 x64

@CryptoSiD
Copy link

CryptoSiD commented Mar 9, 2025

Just tried nightly, still the same

 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:1TJuuyMDGWibVO19FUGyNDUXMCa4p3H8Q1njHQWLDCI 
 SSH  Trying private key: file://O:\Nextcloud\sys\ssh\docker-vm\id_rsa
 X  Authentication rejected

on win11 x64

Same here!

 SSH  Host key fingerprint:
 SSH   ssh-rsa  SHA256:/3cGWf2H2AyyIQ20GM3dTlmMozHZG14LPNlcdQD7n1w 
 SSH  Trying private key: vault://4e8e981b99ec6073b1fe066e0a99d8c6dc66eff4e29f886d3e2e466f1b072b38
 X  Authentication rejected

@Eugeny
Copy link
Owner

Eugeny commented Mar 10, 2025

I've updated the build, could you give it another try?

@hugalafutro
Copy link

hugalafutro commented Mar 10, 2025

Image
works ok on win11 \o/

thanks for the fix. now to wait till it updates in aur and chaotic-aur :D

@jack-y
Copy link
Author

jack-y commented Mar 10, 2025

Workflow build.yml | Branch master | Artifact Linux DEB (amd64) 1.0.223-nightly

Works on Ubuntu 24.04. Thank you so much @Eugeny!

@mattia-donato
Copy link

I tried the nightly build and it do not change the bug is still there.

Tested on Linux Linux Mint 21.3 (based on Ubuntu 22.04) and there is the same error in 1.0.223+nightly, 1.0.222, 1.0.221, and even 1.0.215, this means that is not related to the russh. I tried also to remove the ~/.config/tabby configurations or keeping it.

I tested the 1.0.223+nightly also on Windows 10.... exactly the same problem.

I can still connect to SSH through the terminal ssh MYSSHUSER@IPMYSERVER but when I try to access by Tabby ssh MYSSHUSER@IPMYSERVER I get authentication error... The only way to access ssh on Tabby for me is by calling a profile with saved password in it.

 SSH  Connecting to ssh MYSSHUSER@IPMYSERVER
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:pjgEtO3Imynicekeeeeeeeeeeeeeeee3NhSxDHnaii4 
 SSH  Trying private key: id_rsa

 SSH  Connecting to ssh MYSSHUSER@IPMYSERVER
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:pjgEtO3Imynicekeeeeeeeeeeeeeeee3NhSxDHnaii4 
 SSH  Trying private key: id_rsa
 X  Authentication rejected

@AutisticShark
Copy link

Nightly build 5deb725 fixed the issue for me, Windows 11 24H2.

@mattia-donato
Copy link

I used this link https://nightly.link/Eugeny/tabby/workflows/build/master/Linux%20DEB%20%28amd64%29.zip... does it correspond to the nightly build 5deb725 ?

@mattia-donato
Copy link

mattia-donato commented Mar 10, 2025

@Eugeny I found the bug!! The problem is not the password but the username! Tabby uses a wrong username to log in SSH: in tabby-ssh/dist/index.js, I noticed that the authUsername in start() is ssh myuser, instead of being myuser.

I found a quick and dirty workaround and finally I can use it locally but I do not have idea how to fix in a proper way!!

            if (!this.authUsername) {
                const modal = this.ngbModal.open(external_tabby_core_.PromptModalComponent);
                modal.componentInstance.prompt = `Username for ${this.profile.options.host}`;
                try {
                    const result = yield modal.result.catch(() => null);
                    this.authUsername = (_r = result === null || result === void 0 ? void 0 : result.value) !== null && _r !== void 0 ? _r : null;
                }
                catch (_u) {
                    this.authUsername = 'root';
                }

           // ============= WORKAROUND ========================
            if (this.authUsername.startsWith('ssh ')) {
                this.authUsername = this.authUsername.substring(4);
            }
           // ========END WORKAROUND ==========================

            if ((_s = this.authUsername) === null || _s === void 0 ? void 0 : _s.startsWith('$')) {
                try {
                    const result = process.env[this.authUsername.slice(1)];
                    this.authUsername = result !== null && result !== void 0 ? result : this.authUsername;
                }
                catch (_v) {
                    this.authUsername = 'root';
                }
            }

and it works.

@AutisticShark
Copy link

AutisticShark commented Mar 10, 2025

https://github.com/Eugeny/tabby/actions/runs/13758597414

GitHub
A terminal for a more modern age. Contribute to Eugeny/tabby development by creating an account on GitHub.

@waska14
Copy link

waska14 commented Mar 10, 2025

Same here:
Tabby Version 1.0.222 (1.0.222)
Macbook Pro M2 15.3.1 (24D70)

 SSH  Connecting to ip_here
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  SHA256:d3UD/LIAUJSIOHJOIEJlqkwesjaskldjalsejO+3Ke7g 
 SSH  Trying private key: id_rsa
 X  Authentication rejected

Anyone has found any solutions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests