2 ms·
Show HN: torbb – Now with Tor, run BrowserBox as a hidden service instantly
- keepamovin 3y agoHello again, HN Community! I'm excited to share something intriguing: Hidden services offer enhanced privacy and security, with anonymized server locations and end-to-end encrypted communications, as well as globally unique hostnames without DNS attestation, making them ideal for secure, censorship-resistant web interactions. You can now create a Tor Hidden Service running BrowserBox directly from GitHub actions! Just fork or generate a copy of the BrowserBox repo, open the "BrowserBox Tor Hidden Service" issue, and the process kicks off automatically. Within a few minutes, an onion link will be posted in the issue comments. It's straightforward, requires no additional configuration, and runs on your GitHub Actions free minutes. Let me dive into a key aspect of this update: Implementing HTTPS in the unique environment of a Tor hidden service. While the go-to solutions like Let's Encrypt shy away from .onion domains for privacy reasons, this presents a challenge for those seeking privacy-enhanced browsing on Tor. My solution? I've opted for self-signed certificates. Despite browser warnings, they offer secure data encryption, which is crucial, even over Tor's anonymous network, especially at exit nodes. To facilitate this, I provide a rootCA.pem file (created per installation by mkcert -install) with an installation guide, balancing security with ease of use. Here's a idea: if Let's Encrypt can authenticate over HTTP for certificates, why not extend this to onion services? It seems feasible, yet .onion domains remain underserved in this aspect. For BrowserBox users, it's a personal choice on whether to install rootCA.pem. Installing it smooths out the browsing experience, but it also means extending trust to the CA. Choosing not to install maintains higher security at the cost of some convenience and feature limitations. In essence, my approach with BrowserBox is to balance security and accessibility, keeping it user-friendly on the Tor network. It's a tailored solution, aligning with BrowserBox's ethos and the complex nature of online privacy and security. I'd love to hear your thoughts on the future of HTTPS in the Tor landscape and how we can collectively push for equal access to privacy and security tools, even in the hidden corners of the internet. Have a good one! :) Cris