EnFuzion has little to no security. It uses telnet and rsh to connect to the nodes in its local cluster that have been proven insecure. This connection method was chosen by the EnFuzion developers to reduce communication time of connecting to its nodes. If encryption or compression were used, they would add unwanted delay connecting to the nodes. Because of this, EnFuzion is normally configured behind a firewall. Access is given to cluster's host and access is gained to the nodes from there.
Because the Multi-Site EnFuzion client works by connecting to multiple clusters, the communication delay between the clusters will increase, as different clusters are normally distant. To avoid delays in long file transfers, compression can be used. Further to this, to enable access to clusters across insecure network, encryption is also needed.
The solution was to use SSH. SSH allows for both encryption and compression and has been designed as a replacement for telnet and rsh. Using SSH we were able to establish a secure connection to the remote clusters and launch EnFuzion. SSH also has the ability to redirect sockets down the secure channel. This allowed us to connect to the EnFuzion's command port to control the current run as if we connected from that computer. Most security configurations only allow a socket connection from within the cluster.