Pointers to NX design which helps mitigate X11 display sniffing?

[dazzling_poitras]

Howdy, folks.

I’m doing some work to eval NX for use in my org and I’d like to better understand how NX helps mitigate some of the concerns around X11 display sniffing which present when using, by comparison, SSH w/ X11Forwarding. My understanding is that its not just clever use of the underlying SSH tunneling infrastructure but also something about the design of NX itself and probably something to do with a virtual X11 server?

I’ve done a fair amount of searching about and other than a handful of heated arguments over on the [removed] mailing lists I’ve not found a lot.

The exact consideration is preventing X11 information from the local node from being exposed to the remote node when the two have established an NX session.

ty!

 

[Britgirl]

Hi, it’s impossible given that NoMachine encrypts all traffic end to end, including X11 protocol when used. You can take a look at the following article which explains how NoMachine handles security and encryption, https://kb.nomachine.com/AR04S01121. Some other pointers can be found in this article https://kb.nomachine.com/AR11K00745 published at the time we transitioned away from our legacy version.

[Author]

Posts