Why Medis can not use a default SSH key in SSH tunnel

[shiny]

I have a default key file in ~/.ssh/id_rsa, must set the key in Medis.
How about try the default SSH key, is that a good idea?

[luin]

That's definitely a good idea!

[ottonet]

Yep, please add! Next to that I find it impossible to browse to ~/.ssh/id_rsa from the finder window medis shows when you click on the key symbol, as hidden folders are not shown. You might want to default to ~/.ssh when clicking on the key symbol...

Had to create a symbolic link ln -s .ssh ssh to actually be able to browse to ~/.ssh/id_rsa

[luin]

There are two ways to browse to ~/.ssh/id_rsa in the finder window before medis's supporting the default ssh key path:

1. Command + Shift + '.' to show the hidden files.
2. Command + Shift + G and enter ~/.ssh

[alexbeletsky]

@luin thanks a lot, that's exactly what I need. I +1 for @shiny default key idea!

[ctf0]

@luin i did just that and was able to select the file however

SSH Error: Cannot parse privateKey: Unsupported key format

note am using ssh-ed25519 for keys

[luin]

Did you select a public key or a  private key?
Get Outlook for iOS

On Sun, Oct 30, 2016 at 4:13 AM +0800, "Muah" notifications@github.com wrote:

@luin i did just that and was able to select the file however

SSH Error: Cannot parse privateKey: Unsupported key format

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[ctf0]

both gives error

[ctf0]

@luin any news ?

[luin]

@ctf0 Sorry for the late response. Could you please generate a new private key in the same format and post it here so I can debug locally?

[ctf0]

just follow this steps to create an Ed25519 key https://blog.g3rt.nl/upgrade-your-ssh-keys.html

[luin]

@ctf0 It turns out ed25519 hasn't been supported by the upstream modules: mscdex/ssh2#352. I'm going to support ECDSA format first and would like to look into the support for Ed25519 key.

[ctf0]

can u give any time frame for that ?

[pehbehbeh]

SSH Tunnel feature is basically unusable...

I get SSH Error: Cannot parse privateKey: Unsupported key format for all keys I tested...

[luin]

@pehbehbeh Are you using private keys or public keys? Private keys are required for SSH Tunnel.

[pehbehbeh]

I used private keys and tried rsa and ed25519.

[luin]

@pehbehbeh My apologies. Ed25519 hasn't been supported yet as mentioned above.

[pehbehbeh]

I also get the error with "standard" RSA key.

SSH Error: Cannot parse privateKey: Unsupported key format.

[pehbehbeh]

How do you generate a working key? Maybe I can test that on my machine.

[luin]

@pehbehbeh https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key.

[pehbehbeh]

That's how I always generate SSH keys. Does not work for me... 😐

[luin]

@pehbehbeh Could you send me a private key you generated so I can test it.

[katamaran1993]

Hi all, because need to use Pro tools like FastoRedis which support password/keys and ssh tunnels into visible network from remote server.

[intrepidws]

@luin After upgrading to Mojave, I'm not experiencing the same problems as everyone else here. I cannot get any SSH key to work. I generated the SSH key using the GitHub link that you provided and that still won't work. Any ideas?

[intrepidws]

OK so I was able to solve this. From my (limited) understanding, Mojave uses a different SSH key format by default (RFC4716) but you have to use the PEM type for it to work with Medis.

To generate a new key with this, run:
ssh-keygen -m PEM -t rsa -b 4096 -C "your@email.com"

Or to convert an existing key, run:
ssh-keygen -p -m PEM -f ~/.ssh/id_rsa

Hope this helps!

[luin]

Medis 2 already supports providing an SSH config file: https://docs.getmedis.com/settings/custom-ssh-config so closing. Free free to create a new issue if there are anything else we can improve!