Robomongo: Ubuntu 20.04 support

[ignl]

Hi, after upgrading server to Ubuntu 20.04 ssh tunnel stopped working.

[harshmandan]

+1 Updated my server to 20.04 yesterday and wasted 2 hours trying different firewalls configs and even different software. Can't connect to my server.

With port 22/23: Error: Error when starting up SSH session: -8

[maikeldotuk]

Same problem. I'm going to add I have absolutely no trouble with another machine with Ubuntu 18 that has a different version of SSH.

Working: OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016
Not-working: OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f 31 Mar 2020

[pplytas]

Same here. Spinned up a fresh VM with Ubuntu 20.04 and SSH tunnel could not connect.

Error Details:

Failed to create SSH tunnel to 104.248.21.193:20.

Error:
Operation timed out. Failed to connect to 104.248.21.193:20. (Error #60)

[maikeldotuk]

Hi @pitpitpat , my solution was to scrap that machine and install instead Ubuntu 18 on it. For some reason, which I think has to do with the OpenSSH version, it work flawlessly there. I couldn't find any major difference in the standard OpenSSH configuration of machines with Ubuntu 18 and Ubuntu 20 that could block Robo3T in any way.

So for now, my solution has been to downgrade ubuntu.

[simsekgokhan]

Hi @ignl and all, thanks a lot for reporting the problem.
We did reproduce the problem. And it is reproducible even with the currently developed Robo 1.4 which uses latest openssl-1.1.1f and latest libssh2 1.9.0. We will have to investigate more to understand the root cause of this problem.

And as a workaround, SSH port forwarding can be used: https://github.com/Studio3T/robomongo/wiki/How-to-use-SSH-port-forwarding-with-Robo-3T. Not the best solution but it is easy and works.

[simsekgokhan]

We have done a little bit more testing with Ubuntu 20.04. SSH connection worked after adding public key into server authorized_keys file. If someone wants to try, this solved it:

// SSH server:  
~/.ssh/authorized_keys // public keys of clients this server trusts, one line per key
ssh-rsa <client-pub-key>

Important: Currently DSA, RSA keys are supported. Robo 1.4 is being develped to support ECDSA and Ed25519 keys. PPK keys must be converted to OPENSSH format.

[maikeldotuk]

Sounds interesting, will give it a try tonight (Spain time) On 13 Jul 2020 16:45, Gökhan Şimşek [e-mail] wrote:
We have done little bit more testing. SSH connection worked after adding public key into server authorized_keys file. If someone wants to try, this solved it:
// SSH server:
~/.ssh/authorized_keys // public keys of clients this server trusts, one line per key
ssh-rsa

Important: Currently DSA, RSA keys are supported. Robo 1.4 is being develped to support ECDSA and Ed25519 keys.

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

[harshmandan]

Waiting for ecda key support eagerly!

[pplytas]

We have done a little bit more testing with Ubuntu 20.04. SSH connection worked after adding public key into server authorized_keys file. If someone wants to try, this solved it:

// SSH server:  
~/.ssh/authorized_keys // public keys of clients this server trusts, one line per key
ssh-rsa <client-pub-key>

Important: Currently DSA, RSA keys are supported. Robo 1.4 is being develped to support ECDSA and Ed25519 keys. PPK keys must be converted to OPENSSH format.

@simsekgokhan
The issue seems to persist when using SSH tunnel option, even after adding the public RSA key to the server's authorized_keys file.
Tested on MacOS 10.15.5.
Server is running Ubuntu 20.04 (on DigitalOcean)

[maikeldotuk]

Right, so RSA key was already on authorised keys on test server with Ubuntu 20.04, the proposed solution same as for @pitpitpat didn't work. The problem still exists.

[harshmandan]

@maikeldotuk Any update on this?

[maikeldotuk]

It still doesn't work for me. On another system I can't afford to downgrade Ubuntu, I've tried everything and robo3t can't connect while nosqlbooster simply connects with no issue.

---

From: Harsh Mandan [e-mail]
Sent: Friday, August 28, 2020 10:11:23 AM
To: Studio3T/robomongo [e-mail]
Cc: Miguel Frias Mosquea [e-mail]; Mention [e-mail]
Subject: Re: [Studio3T/robomongo] Ubuntu 20.04 support (#1726)

@maikeldotukhttps://github.com/maikeldotuk Any update on this?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Studio3T/robomongo/issues/1726#issuecomment-682391870, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHAYX5OV7XC5TEXFJDL7ILLSC5RCXANCNFSM4MATXMSA.

[maikeldotuk]

So for that system I'm using nosqlbooster. I have no other option.

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: [email protected] [e-mail]
Sent: Friday, August 28, 2020 10:17:22 AM
To: Studio3T/robomongo [e-mail]
Subject: Re: [Studio3T/robomongo] Ubuntu 20.04 support (#1726)

It still doesn't work for me. On another system I can't afford to downgrade Ubuntu, I've tried everything and robo3t can't connect while nosqlbooster simply connects with no issue.

---

From: Harsh Mandan [e-mail]
Sent: Friday, August 28, 2020 10:11:23 AM
To: Studio3T/robomongo [e-mail]
Cc: Miguel Frias Mosquea [e-mail]; Mention [e-mail]
Subject: Re: [Studio3T/robomongo] Ubuntu 20.04 support (#1726)

@maikeldotukhttps://github.com/maikeldotuk Any update on this?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Studio3T/robomongo/issues/1726#issuecomment-682391870, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHAYX5OV7XC5TEXFJDL7ILLSC5RCXANCNFSM4MATXMSA.

[simsekgokhan]

Please also see: https://github.com/Studio3T/robomongo/issues/1189#issuecomment-447109457 and https://github.com/Studio3T/robomongo/issues/1590#issuecomment-475954939

[ufoproger]

Step-by-step workaround based on https://github.com/Studio3T/robomongo/issues/1189#issuecomment-750128888.

Tested for OpenSSH server 8.3+ (installed on Ubuntu 20.04 and newer, Arch Linux etc).

You need to add legacy key exchange algorithm diffie-hellman-group14-sha1 to OpenSSH server (parameter KexAlgorithms):

1. Get default value of parameter KexAlgorithms: run man 5 sshd_config (example):

    ...

    The default is:

        curve25519-sha256,[email protected],
        ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,
        diffie-hellman-group-exchange-sha256,
        diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,
        diffie-hellman-group14-sha256

1. The current value of the parameter KexAlgorithms is curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256;
2. Append legacy kex algorithm diffie-hellman-group14-sha1 to the parameter from above;
3. Add the resulting parameter to the end of the file /etc/ssh/sshd_config:

KexAlgorithms curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1

1. Test configuration: sshd -t;
2. Reload OpenSSH server: systemctl reload sshd or service sshd reload etc;
3. enjoy using the built-in Robo 3T SSH tunnel :)