Today, we are officially introducing a proof-of-work (PoW) defense for onion services designed to prioritize verified network traffic as a deterrent against denial of service (DoS) attacks with the release of Tor 0.4.8.
A new DoS protection mechanism for Tor leveraging Proof-of-Work.
This is a pretty excellent use case for PoW. I could see this being adopted by other DDoS services, server stacks, and eventually make its way into openwrt, pfsense etc.
How would you add it to pfSense, or any other firewall?
Tor can add it to their service, and all clients that wants to use the Tor service needs to implement the same feature. If Netgate added this to the internet protocols, no other device would be able to communicate with pfSense, unless they also used this special network stack.
If Netgate added this to the internet protocols, no other device would be able to communicate with pfSense, unless they also used this special network stack.
I mean technically that’s also the case with the Tor protocol.
This is a pretty excellent use case for PoW. I could see this being adopted by other DDoS services, server stacks, and eventually make its way into openwrt, pfsense etc.
How would you add it to pfSense, or any other firewall?
Tor can add it to their service, and all clients that wants to use the Tor service needs to implement the same feature. If Netgate added this to the internet protocols, no other device would be able to communicate with pfSense, unless they also used this special network stack.
I mean technically that’s also the case with the Tor protocol.