This is a C/P that has been approved by the Nfusion Development Team.
Quote: There is lot of rumors going on if *** is secured. Well in short it is - and then it is not. Just to give you a few points on security with ***:
1) *** runs on a centralized server that is a share point to servers which relay on this server. Your box is connecting too relays not the *** Server.
2) *** servers require UDP connection, not TCP. You can think of UDP as more secure, but the real difference is that UDP packets travel one way (request is sent from the receiver and then fullfilled by the server but there is no guarantee on data delivery of the packet from the server, meaning that the server drops the link with requestor as soon as it gets it - it may deliver it later on however). The relay - is really a relay in UDP sense - (requests can be made to one server but another server may fullfill it). Since there is no constant connection being open it is almost impossible to catch the very small (tidy) request and data travel from boxes to ***.
3) *** Servers accept only connections that have a receiver ID attached to the data package. No request from PC or other device can be made - this really gives much trouble in identifying what the content is of the *** package or intercepting it. I am not sure if the package itself is being encrypted somehow - but it will be easy to do if it isn't. With encrypted packages, even if someone intercepts it - that interception would become useless.
4) In order for the providers to hunt you down they will need to know what servers that nFusion boxes are connecting too. To find out, they will have to intercept the traffic from the centralized server which is located off-shore (but hard to do explained before). I could not locate the servers by looking at the routers access logs - I can only find the servers it is connecting too --- and surprisingly I saw many different connections (rotating relays) --- which gives me positive vibes about ***.
5) All the providers can do is see that your connection is making some request for data that is being transfered from a server and has been identified as suspicious - but before they can even take any action upon it - the new server can be re-set and there you go, another round of finding it again will be needed. This is time consuming and very very tidious and an expensive task (not that the providers cant afford it). Even if the provider proves that the traffic from your internet connection is suspicious - they can not prove that it came from your requests and your receiver (they cant trace back anything beyond your router/modem).
6) "Dave" did go to after the small people on the first occasion of *** (more then 10 years ago -- ohhh yes do not be surprised *** is nothing new --- it has been used back in Dave days when a computer was needed that will serve already descrambled packages to the receiver using waffer boards or card emulators) - but "Dave" had to physically prove that this was happening from people trying this (hardware needed to make this function) - unlike today (no additional hardware is needed - so hard to tell if you are really doing anything wrong).
The final decision is always up to you to make. I do not want to sound encouraging or disappointing - use your own judgment - do lots of reading