1235937 - (tor_onion_access) [meta] set up tor onion service (.onion) anonymous access to our network services

Status: RESOLVED WONTFIX

(Infrastructure & Operations :: Infrastructure: Other, task)

Description

[Dave Huseby [:huseby]]

Can we set up .onion access to our network services?

bugzilla.mozilla.org
irc.mozilla.org
www.mozilla.org
addons.mozilla.org
developer.mozilla.org
people.mozilla.org

Let's generate a vanity .onion using Shallot that starts with mozilla*.onion and then add it to our EV certificate.

Existing .onion services:
Facebook: https://facebookcorewwwi.onion
DuckDuckGo: https://3g2upl4pq6kufc4m.onion/
Debian: http://vwakviie2ienjx6t.onion/

There's also a great talk on .onion services that was given by Tor project people at 32c3 this week.

Comment 1

[Jake Maul [:jakem]]

I'm guessing the talk is this: https://www.youtube.com/watch?v=oh9D2r-ck40

Comment 2

[Brian Hourigan [:digi]]

:huseby,

Thanks for the request. Can you tell me more about the use case? Would an onion address provide something that a tor exit node can't?

Comment 3

[Dave Huseby [:huseby]]

The compelling reason to deploy and maintain .onion access to our web properties has to with how the Tor network is organized.  Exit nodes in the Tor network are the primary bottleneck in terms of bandwidth.  If we provide .onion access, then accessing our web properties anonymously over the Tor network will not consume any of the bandwidth of the exit nodes.

Comment 4

[Corey Shields [:cshields]]

We won't be resourcing any tor connectivity in IT-managed services so I'm going to close this out.