SPN Testing Goals and Status

⚠ The SPN is in broad testing phase. Please be aware that we cannot guarantee full privacy until all aspects have been thoroughly tested and confirmed.

updated for SPN v0.3.0

Testing Goals

• Portmaster v0.7.0 / SPN v0.3.0:
  • Should work:
    • Check if the Portmaster can successfully connect to the SPN.
    • Normal browsing of websites.
  • Under investigation:
    • Big file downloads.
    • Video streaming.
    • UDP based applications.

Known Issues

• ⚠ The SPN re-uses connections to nodes. Due to missing route evaluation during routing calculation we currently cannot guarantee the minimum three hops.
• ⚠ Speeds might vary greatly as we don't know the resource profile of the SPN yet.
• The SPN seems to be failing after sleep/suspend. Investigating. Disable/Enable SPN as a workaround.
• We're leaking open file descriptors somewhere, which also affects Portmaster after some time. Restart Portmaster as a workaround.
• For stability, the client is artificially more sequential in order to provide more stability. This might lead to lag when lots of connections are initiated at the same time. Eg. when browsing to "big" websites.

How To Report Bugs

Please report bugs here.

Next Steps

• Check if existing routes are compatible during routing calculation.
• Configure internal route cost calculation to improve route selection.
• Check exit policy during route calculation to prevent error when connecting.
• Check entry policy when selecting home hub (entry node) to prevent error when connecting.
• Add encryption detection and limit unencrypted connections to trusted hubs (nodes).
• First performance improvements.