Problem connection via SSH bastion host with passphrase protected ed25519 key

[christos]

Maybe related to #532

What did you do?

• I set up a connection for connecting to my AWS RDS database at db.XXXXX.com that is only accessible from a bastion host bastion.YYYYYY.com

What did you expect to happen?

• I clicked on Connect and I expected to connect to the database.

What actually happened?

I got this error:

What software versions are you using?

Postico version: Version 1.4beta2 (2737)
(I know, it should say Beta3, but it says Beta2)
macOS version: 10.13.4
PostgreSQL version: (never connected)

Extra information

I can ssh to the bastion host from the command line without issue: ssh -v ec2-user@bastion.YYYYYY.com and the debug output verifies that the ~/.ssh/id_ed25519 key is the one offered and accepted. The key has a passphrase but it is saved in the keychain. Postico never prompts me for the passphrase.

I've also tried the same connection setup with another GUI client and it works correctly. Another thing that works in the other client but not in Postico is that I can use the following .ssh/config shortcut and only specify Bastion as the host (no need for FQDN, user, key specification).

Host Bastion
  Hostname bastion.YYYYYY.com
  User ec2-user

Postico doesn't resolve the connections details from .ssh/config

[jakob]

Thanks a lot for the info. I was able to reproduce this. It appears that there is an issue with passphrase-protected ecdsa and ed25519 in libssh2 (Postico 1.4 beta is using an unstable branch of libssh2).

As for the lack of support for .ssh/config, that's a known limitation.

[jakob]

PS: If you want to claim your free license (we are currently running a bug bounty for Postico 1.4 beta), please send me the name/email you want on your license to jakob@eggerapps.at

[postico-bot]

We have been working on this issue!

jakob: libssh2: Fix issue where Postico did not prompt for passphrase of private key #544

Download Build B2750, or check out the list of recent builds.

[martinjankoehler]

Hi,

thanks for reporting, we hope this is fixed with Postico 1.4 Beta 4, please download Build 2755.

Please let us know if you still encounter problems!

Best regards,
Martin

[christos]

I can confirm this issue has been fixed! 💯