Use `SSHJ` implementation by default to support ed25519 keys

System information:

• Operating system (distribution) and version – doesn’t matter (in my case, latest macOS)
• DBeaver version ersion 22.0.0.202203060510)
• Additional extensions

Connection specification:

• Database name and version Postgres, doesn’t matter
• Driver name Postgres driver (default one)
• Do you use tunnels or proxies (SSH, SOCKS, etc)? SSH port forwarding – it works well but only with RSA or .pem keys. If I use ed25519, it fails

Describe the problem you’re observing:

invalid privatekey: [B@3e17e4ee – see screenshot:

Steps to reproduce, if exist:

Straightforward – just use an ed25519 key

Include any warning/errors/backtraces from the logs

N/A

Additional info

https://mkyong.com/java/jsch-invalid-privatekey-exception/ and https://github.com/dbeaver/dbeaver/search?q=JSch&type= tell that the problem is most likely in the lib JSch that doesn’t support ed25519. At the same time, this format is becoming more and more popular, and our (Database Lab) users start to complain about the inability to work with Postgres thin clones from DBeavier when SSH port forwarding is a requirement. Please fix it.

[E1izabeth]

Hello, @NikolayS! Have you tried to switch to another ssh library used to establish connection tunnel? It can be done in Advanced settings:

[NikolayS]

Maybe SSHJ could become the default?