3 ms·
This is what I've always done when I was a poor student and didn't have a public IP. The latency can be painful but it's way better than nothing. I will say y
by swiley 6y ago
This is what I've always done when I was a poor student and didn't have a public IP.
The latency can be painful but it's way better than nothing.
I will say you should probably be careful about running a webserver on TOR. Almost all my machines have a basic web server just for copying static files to windows hosts I don't want to give my password to. People would find these on TOR and then find my resume, I got plenty of emails asking to set up "hidden sites on the dark web for sharing pictures."
- yjftsjthsd-h 6y agoIf it's just for personal use, you can and should use client certificates to ensure that you're the only person who even can connect.
- swiley 6y agoThen I would have to generate certificates and leave them on random people's machines. Plus when I'm sharing things with other people I can't just send them a link, I have to explain how to install the certificate into their browser (or OS in some cases.) On top of all that openssl is very complex and has had serious CVEs before, I'd feel a lot less comfortable exposing that to TOR than a smaller web server.
- yjftsjthsd-h 6y agoI don't mean HTTP client cert in the web server/browser, I mean the TOR built-in option that you enable with `HiddenServiceAuthorizeClient stealth list,of,client,names`. Granted, this does mean that you have to distribute keys (but you were already distributing an onion address) and there's more setup complexity (although you already have to run TOR, so we're not in "normal user" territory anyways).