3 ms·
I'd really like to see more technical discussion of Safing's SPN idea and implementation (https://safing.io/spn/ https://safing.io/spn/). If I've understood it
by toomanyusers 4y ago
I'd really like to see more technical discussion of Safing's SPN idea and implementation (https://safing.io/spn/ https://safing.io/spn/). If I've understood it correctly, it seems to be in-line with the general trajectory of where Cloudflare is going with DNS privacy and Apple is going with its relay service.
It seems obvious that VPN services should be split into Relay and Exit services so that you don't have to necessarily trust a single company not to collect and sell all your internet traffic.
- g_p 4y agoFrom a DNS privacy perspective, ODOH (Oblivious DNS over HTTPS) seems to achieve this at protocol level, with interoperability between providers. While there are tunnelled VPN (separate entry and exit), they always seem to be with the same provider. The iCloud private relay design appears to avoid this. It would be interesting to see where SPN goes, and more on how it works, as you say.
- wmf 4y agoIt doesn't even define the acronym!
- dhaavi 4y agoSorry about that. It's "Safing Privacy Network".
- dhaavi 4y agoThe SPN (Safing Privacy Network) aims to fill the area between VPNs and Tor. VPNs provide very little real privacy and Tor is (outside Tor Browser) very difficult to setup and configure. Yes, you are correct, there are similarities there. Except of course that SPN is open source. We do have a white paper: https://safing.io/files/whitepaper/Gate17.pdf https://safing.io/files/whitepaper/Gate17.pdf And YES! I'd love to see more technical discussion of the SPN too. So many things to unpack, to learn and improve.