5 ms·
"Waiting for pair client connection". That'd be something. Interesting thought but I can imagine a range of issues. In the same vein, how about the server woul
by keyle 3y ago
"Waiting for pair client connection". That'd be something. Interesting thought but I can imagine a range of issues.
In the same vein, how about the server would hold a pool of IPs in which the client has to return a proof of port knocking? e.g. here is a token, send that to this IP:port and wait for a unique response I can verify. Call this proof of latency. It would be low CPU, would spread the load across various machines and ports. On the downside, of course, you need multiple IPs and potentially servers. It could be implemented on the same machine but that would shift the cpu load to port connections.
- dmurray 3y agoWhat does this prove about the client? Just that they have a reasonably fast connection (which in TOR-world can be painful to achieve), not that they aren't part of a botnet. It allows you to scale your workload, but "just pay for more servers and outscale the attacker" isn't generally an acceptable way to deal with DDOS.