Not that we couldn’t use a UDP side-channel with SSH, but it would have been hard to explain to managers in a company that, yes, we use SSH for the connection but then most data is not going through SSH.

Not so with the NX protocol.Īdditionally, when using the NX protocol, audio and video can use UDP. We can’t provide the details, but we were in a situation where a display packet, to come to the client, had to traverse 12 processes and be encrypted 3 times. With NX we can simply hand over the SSL context from one process to the next (as Apache does) and relay connections by only running encryption end-to-end. Then with SSH we have processes communicating through pipes (like multiple separate commands piped in a shell), so we are adding a further encryption stage at each hop. This is an additional process for each machine traversed, so in a multi-node server there are at least two. Tunneling over SSH means that our packets have to traverse at least 1 additional process before coming to the destination (at least the SSHD process, if we don’t run a separate SSH client).

There are multiple reasons for using our own protocol rather than SSH. All products use the NX protocol as default.

The products targeting commercial use, so both of the Enterprise Server and Terminal Server families, additionally support the SSH protocol out of the box. 4, NoMachine implements its own protocol for secure communication over the network.

Install nomachine divps aruba