SSH Key | Could Not Parse Key on import

General Legacy Apps
,
1

Using Core Proxy 16.03
Anytime I try to import key I am getting a Could Not Parse Key error.
Key is generated using ssh-keygen method - tried adding -pem same problem

Is this a bug in core proxy?? I am an shh beginner so trying to figure out if this is "user error"

Any ideas??

DL

2

Could you please extract some lines from you private key file? For example:

-----BEGIN DSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,AF79F9904FBFC4E0

Above insensitive information should enough for me find out the real cause.

Yang

3

I am not using DSA since it's older protocol... Generated with:

ssh-keygen rsa -t

Output is as follows:

-----BEGIN OPENSSH PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAA2048charsxxx
-----END OPENSSH PRIVATE KEY-----

4

I should mention... The key imported normally and was able to connect in Core Tunnel - but using same key and server in ssh proxy brings up could not parse error.

5

SSH Proxy may not recognize a private key generated with recent tools, after all SSH Proxy hasn't been updated in 5 years.

Here I answer you another question asked here:

Core Tunnel may incorporates SSH Proxy features in future release, we're still exploring the feasibility of merging. Since they have different goals, so simply combine both features can make design conflicts.

I'd recommend you use Core Tunnel and create a dynamic port forwarding instead at present.

Yang