SSH problems? Try this experimental build

[Eugeny]

If you're having issues with SSH authorization, performance or connecting to specific hosts, try out this experimental branch:

👉 https://nightly.link/Eugeny/tabby/workflows/build/russh 👈

It includes a new experimental SSH backend based on russh

This build has all the features of the stable Tabby' SSH client!

New stuff available only in that build:

• chacha20-poly1305 cipher
• 3DES-CBC cipher (for old Cisco hardware)
• remembering answers to password prompts in keyboard-interactive auth

I would appreciate any feedback on that build, even just a comment if everything works fine!

[Clem-Fern]

Hey @Eugeny

I hope you are doing well.

I'm using this build. It seems to work great so far.

However, I have some performance issue when using commands like more, tail, show logs.
Output is pretty slow. I'll try to upload a performance record asap.

[Clem-Fern]

After a week using this build, a list of issues I got:

• I can't connect to server using private key anymore. The passphrase prompt is not displayed.

SSH  Loading private key: file:///home/clem/.ssh/my_private_key
SSH   !  Failed to load private key file:///home/clem/.ssh/my_private_key: Error: Keys(KeyIsEncrypted)

From debug console

21:43:41.019 /opt/Tabby/resources/builtin-plugins/tabby-core/dist/index.js:15841 [ssh-x.x.x.x] Loading private key: file:///home/clem/.ssh/id_X
21:43:41.021 /opt/Tabby/resources/builtin-plugins/tabby-core/dist/index.js:15841 [ssh--x.x.x.x]  !  Failed to load private key file:///home/clem/.ssh/id_X: Error: Keys(KeyIsEncrypted)

• Tabby does not detect when sessions are disconnected. Status indicator stills green.

• Output is pretty slow and jerky when using commands like more, tail, show logs. Same problem with the latest release. So not related to this build. Sadly, I can't save performance profile because of a bug (related to [Bug]: Can't save performance traces from the performance tab in DevTools electron/electron#39818 I assume)...

[Eugeny]

Saving performance traces is now fixed in the latest nightly: nightly.link/Eugeny/tabby/workflows/build/master

[ozairakhlaq]

Hi, I have a similar problem with Cisco devices when using the latest build. Came across this while searching. When will this be released as stable?

[Eugeny]

Hopefully soon, I still need to test it more

[Clem-Fern]

I'm using this build for one month now. Working fine for me.

Have you change anything which could help with performance issues (slow output) ? It seems better with the latest build. I can't say for sure yet, lags were a bit random.

[Eugeny]

I haven't changed anything significant, but you should now be able to save a performance trace since that's fixed.

[Clem-Fern]

I haven't changed anything significant, but you should now be able to save a performance trace since that's fixed.

Weird then...

Great ! I'll keep you update if i have issues again.

[peix187]

Hi,

I have a problem with the last build v1.0.211 and this release. The user set in the .ssh\config is not used.
I use the ssh config file C:\Users\xxx.ssh\config on Windows 11 23H2 22631.4037.

Host srv-a
    Hostname 172.22.0.1

Host srv-*
    User admin
    IdentitiesOnly yes
    IdentityFile ~/.ssh/mysshkey

When i select the profile srv-a imported from .ssh\config the user is not admin but root (i see this on the top of the screen [email protected]:22).
On a new terminal in Tabby, if i run ssh srv-a the user used is admin.
The problem seems to be located on the parsed elements because when i add User admin in the section of srv-a the user used is good.

[Eugeny]

russh backend is now included in the normal nightly build