4 ms·
> It's very easy to manage incoming bandwidth when you're hosting a tor onion service. Yeaah, I don’t think anyone who’s operated a larger onion service would
by ryanlol 7y ago
> It's very easy to manage incoming bandwidth when you're hosting a tor onion service.
Yeaah, I don’t think anyone who’s operated a larger onion service would agree with you.
- superkuh 7y agoWell, I've been operating a bunch of small ones from a home connection. So my bandwidth issues might be of less scale but certainly more acute. One simple line of Tor config allows me to limit my total bandwidth and avoid saturating my home connection due to people hitting the onion services. I've had one that's been under a DoS for about a month now and things are going well regardless. Differentiating "real" from "bad" traffic is super hard and almost infeasible, I get what you're saying about that. But in terms of not getting knocked offline Tor is easy and really nice.
- ryanlol 7y ago> But in terms of not getting knocked offline Tor is easy and really nice. That’s of course only until someone who isn’t utterly incompetent tries to DoS you and you realize that you’ll need to spin up hundreds and hundreds of tor daemons (with cpu cores to match!) to tank it. Onionbalance isn’t built in, and hardly solves attacks. There are no DDoS protection services, so you’re left scrambling to build your own infra against impossible odds. None of the big onionland sites manage decent uptimes.