March 2020 - tbb-dev - lists.torproject.org

Turn on geolocation in Tor Browser
by Drew Johnson 25 Mar '20

25 Mar '20

I would like to have geolocation within the Tor Browser turned on. I set geo.enabled to 'true'. If I go to www.browserleaks.org/geo<http://www.browserleaks.org/geo> it does ask for me to allow it, but it always comes back with 'POSITION_UNAVAILABLE'. I have gone through the code in nsGeolocation.cpp and it isn't obvious to me why it is returning this. Do I need to build the browser with some specific switches set? I am using 9.5a7 and building for Windows 64-bit. Thanks Drew

3 2

obfs4 in Tor Expert Bundle (was Re: [tor-relays] Stable flag not appearing on my bridge.)
by teor 19 Mar '20

19 Mar '20

Hi, > On 4 Mar 2020, at 04:21, Keifer Bly <keifer.bly(a)gmail.com> wrote: > > Thx. I was wondering if obfs4 could be included in the same file directory to download tor expert bundle from? Sorry, I didn't see your question until now. Please start a new thread for new questions! The Tor Browser team packages the Tor Expert Bundle. They should be able to answer your question. I've cc'd them on this email. T

1 0

Re: [tbb-dev] [tor-packagers] torbrowser: problems with 9.0.1 source tarball
by Nicolas Vigier 18 Mar '20

18 Mar '20

Hi! I think the best list to discuss Tor Browser build problems is the tbb-dev(a)lists.torproject.org list, so I'm anwsering there. On Fri, 15 Nov 2019, Thomas Klausner wrote: > Hi! > > I wanted to build firefox-tor-browser-68.2.0esr-9.0-1-build2 > (torbrowser 9.0.1) on NetBSD from the source tarball, but I stumbled > over a couple problems. > > The first one, .mozconfig contains --disable-eme but configure doesn't like it: > > mozbuild.configure.options.InvalidOptionError: --disable-eme is not available in this configuration > > Is this a NetBSD-specific issue or more general? In our linux, windows, macOS .mozconfigs we have the line: ac_add_options --disable-eme But I don't remember seeing this error, so it looks NetBSD-specific. > The second one: > > --- begin --- > The error occurred while processing the following file: > > /scratch/security/tor-browser/work/firefox-tor-browser-68.2.0esr-9.0-1-build2/browser/extensions/moz.build > > The underlying problem is we referenced a path that does not exist. That path is: > > /scratch/security/tor-browser/work/firefox-tor-browser-68.2.0esr-9.0-1-build2/browser/extensions/tor-launcher/moz.build > > Either create the file if it needs to exist or do not reference it. > --- end --- > > > The directory browser/extensions/tor-launcher does not exist in the > tarball, which looks like a problem with the tarball to me. This is a change from this ticket: https://trac.torproject.org/projects/tor/ticket/28044 So you can either download tor-launcher, and extract it under browser/extensions, renaming the tor-launcher-$version directory to tor-launcher: https://dist.torproject.org/torbrowser/9.0.1/src-tor-launcher-0.2.20.2.tar.… https://dist.torproject.org/torbrowser/9.0.1/src-tor-launcher-0.2.20.2.tar.… Or you can build without tor-launcher by adding "ac_add_options --disable-tor-launcher" to the .mozconfig. Nicolas

5 6

SOOC (Same Origin Onion Certificates) discussion tomorrow
by Richard Pospesel 10 Mar '20

10 Mar '20

Hi Everyone, The current UX situation around HTTPS-enabled onionsites is not the best: Tor Browser shows security warning splash screens and icons in scenarios that do not warrant them. On top of that, the only way for your onion site to not show these warnings is by getting an EV cert which is only practical if you have the $$$. alecmuffet's SOOC proposal ( https://github.com/alecmuffett/onion-dv-certificate-proposal/blob/master/te… ) does seem to fix these UX problems for us. Though the proposal is still incomplete, we can make forward progress with a prototype implementation as the certificate specification is fully fleshed out. We'll be talking about this tomorrow during the Sponsor 27 meeting tomorrow on Tuesday 10th May @ 1500UTC in #tor-meeting. Please feel free to come by if you wish to discuss. best, -Richard

1 0