Qnet is QNX Neutrino's transparent networking protocol.

It's described in the Using Qnet for Transparent Distributed Processing chapter in this guide, and in the Native Networking (Qnet) chapter of the System Architecture guide.

Security policy and mandatory access controls dictate which processes can communicate with what other processes. Even if there is a security weakness in some driver and an attacker is able to gain access to the system, if they are unable to communicate with the driver, it will difficult to profit from the weakness.

Qnet displays other QNX Neutrino machines on the network in the filesystem and lets you treat remote systems as extensions of the local machine. It does no authentication beyond getting a user ID from the incoming connection, so be careful when running it on a machine that's accessible to public networks.

To make Qnet more secure, you can use the maproot and mapany options, which map incoming connections (root or anyone, respectively) to a specific user ID. For more information, see lsm-qnet.so in the Utilities Reference.