cancel
Showing results for 
Search instead for 
Did you mean: 

Enable ssh V2 on Remote Desktop to NXserver

Thimanjer_
Not applicable

Enable ssh V2 on Remote Desktop to NXserver

Hello,

We used 7.0R4 (build 17289) on our Juniper VPN SSL SA-4500.

We trying to do remote desktop from my vpn ssl connection to a NXserver. We have configure this session under "Terminal Service Resource Profiles" and we used SSH (tcp22) to connect to this NXserver.


When I launch my remote connection I see that SSH V1 is used to established connection to my NX server. But I would like used SSH V2 instead.

Where can I configure this parameter on my Remote Desktop profiles . or at another place but I don't know where.

We have set this parameters, but It change nothing

In Configuration -> Security -> SSL Options -> Allowed SSL and TLS Version -> Accept only SSL V3 and TLS V1 (maximize security)

Thanks you for any answer.

Regards

3 REPLIES 3
SVK_
Regular Contributor

Re: Enable ssh V2 on Remote Desktop to NXserver

Hi,

The IVE supports SSH versions V1 and V2 and uses the following SSH versions: OpenSSH_2.9.9p1, SSH protocols 1.5/2.0, and OpenSSL 0x0090607f.

Check what version is configured on the backend. enable v2 on the backend and verify.

please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks

Regards,

zanyterp_
Respected Contributor

Re: Enable ssh V2 on Remote Desktop to NXserver

There is no way to force sshv1 or sshv2.
The security options that you found are _only_ for data transfer between the user & IVE
Kita_
Valued Contributor

Re: Enable ssh V2 on Remote Desktop to NXserver

Hello Thimanjer,

Logically thinking, the SSL negogation should take the highest encryption level allowed between the two devices. The easiest way to tell who is the cause would be take a TCPDUMP on the SA or backend to see what encryption availables from each device.

From the SA side, I have not heard of any issues about forcing SSLv1. Most likely, this means the backend is only allowing SSLv1 or has a preference to connect SSLv1.