Tor and Onion addresses are one of those things that I feel like I have known about since forever. Still, I never really understood how the Tor Project worked, both organisationally and technically. It is thanks to Avoiding the Internet Achilles’ heel: locking the web open with Onion Services at the Internet Archive Europe that I met some of the main maintainers of Tor software and I had a deeper understanding. I casually chatted with Silvio and Gus after the presentation, and I discovered that they were coming to Rotterdam for their yearly employee get-together! Inevitably, I invited them to host a workshop at XPUB, and they did![1] https://pan.rent/@tommi/117424518467912038 It went very well, and it was incredibly interesting. A perfect and complementary continuation of Thursday’s talk at the Internet Archive Europe. At the end of the presentation, we played a bit with Onion Services, first using OnionShare, then I made some on-the fly experiments. Onionize a website Guided by Gus, who was sitting next to me, I tried to deploy my website as an Onion website. Install The Onion Routing: sudo apt install tor Change the configuration file: sudo nvim /etc/tor/torrc ## Uncomment the following lines and change localhost port # HiddenServiceDir /var/lib/tor/hidden_service/ # HiddenServicePort 80 127.0.0.1:9898 Find the automatically generated .onion hostname: sudo cat /var/lib/tor/hidden_service/hostname Edit /etc/caddy/Caddyfile:[2] tommi.space { header Onion-Location http://sgzx2nsl5e62npnw25oyqrym5fdz42jaklpxjcbwruc2igqymkh6uhyd.onion root * /var/www/tommi.space file_server } :9898 { bind 127.0.0.1 root * /var/www/tommi.space file_server header { -Server -X-Powered-By X-Robots-Tag "noindex, nofollow" } log { output file /var/log/caddy/access.log format json } encode gzip } #TODO: Serve multiple websites via Onion TLS certificate (HTTPS) See the event page on the XPUB Calendar ↩︎ I skimmed this guide as a reference. ↩︎