Tor Browser 7.0 is released

by boklm | June 7, 2017

The Tor Browser Team is proud to announce the first stable release in the 7.0 series. This release is available from the Tor Browser Project page and also from our distribution directory.

This release brings us up to date with Firefox 52 ESR which contains progress in a number of areas:

Most notably we hope having Mozilla's multiprocess mode (e10s) and content sandbox enabled will be one of the major new features in the Tor Browser 7.0 series, both security- and performance-wise (Update (July 7, 12:40 UTC): While sandboxing is enabled in Tor Browser 7 it turns out that the long awaited content sandboxing did not make it into the Firefox ESR series as there were still stability issues with it. We try to backport the necessary patches to make it work for Tor Browser, though.). While we are still working on the sandboxing part for Windows (the e10s part is ready), both Linux and macOS have e10s and content sandboxing enabled by default in Tor Browser 7.0. In addition to that, Linux and macOS users have the option to further harden their Tor Browser setup by using only Unix Domain sockets for communication with tor. Update (June 8, 8:00 UTC): As the last point caused some confusion: enabling Unix Domain sockets alone does not harden Tor Browser. One needs that *and* additional sandboxing mechanisms that prevent communication over TCP/IP.

The highlights in our tracking and fingerprinting resistance improvements are: cookies, view-source requests and the Permissions API are isolated to the first party URL bar domain now to enhance our tracking related defenses. On the fingerprinting side we disabled and/or patched several new features, among them WebGL2, the WebAudio, Social, SpeechSynthesis, and Touch APIs, and the MediaError.message property.

WIth the switch to ESR 52 come new system requirements for Windows and macOS users: On Windows Tor Browser 7.0 won't run on non-SSE2 capable machines anymore. On Apple computers OS X 10.9 is now the minimum system requirement.

Besides new system requirements for Windows and macOS users, there are some known issues with Tor Browser 7.0 as well:

  • Mozilla stopped ALSA support in Firefox 52 for Linux users. This means without having PulseAudio available, sound will be broken in Tor Browser 7.0 on Linux.
  • The download button in the PDF viewer is currently broken. A workaround for this bug is right-clicking on the PDF file and choosing the "Save as" option.
  • Tor Browser has recently been freezing on some websites. This is related to a NoScript bug which will hopefully get addressed in a new NoScript version rather soon. If not then we'll ship a workaround for it in the planned Tor Browser 7.0.1 which will update Firefox to 52.2.0esr next week.

Apart from switching to the new Firefox ESR and dealing with related issues we included a new Tor stable version (0.3.0.7) and updated our NoScript (5.0.5) and HTTPS-Everywhere versions (5.2.17).

We updated our toolchains during the ESR transition as well. In particular we retired the old GCC-based one for our macOS cross-compilation and rely solely on clang/cctools now.

The full changelog since Tor Browser 6.5.2 is:

  • All Platforms
    • Update Firefox to 52.1.2esr
    • Update Tor to 0.3.0.7
    • Update Torbutton to 1.9.7.3
      • Bug 22104: Adjust our content policy whitelist for ff52-esr
      • Bug 22457: Allow resources loaded by view-source://
      • Bug 21627: Ignore HTTP 304 responses when checking redirects
      • Bug 22459: Adapt our use of the nsIContentPolicy to e10s mode
      • Bug 21865: Update our JIT preferences in the security slider
      • Bug 21747: Make 'New Tor Circuit for this Site' work in ESR52
      • Bug 21745: Fix handling of catch-all circuit
      • Bug 21547: Fix circuit display under e10s
      • Bug 21268: e10s compatibility for New Identity
      • Bug 21267: Remove window resize implementation for now
      • Bug 21201: Make Torbutton multiprocess compatible
      • Translations update
    • Update Tor Launcher to 0.2.12.2
      • Bug 22283: Linux 7.0a4 broken after update due to unix: lines in torrc
      • Bug 20761: Don't ignore additional SocksPorts
      • Bug 21920: Don't show locale selection dialog
      • Bug 21546: Mark Tor Launcher as multiprocess compatible
      • Bug 21264: Add a README file
      • Translations update
    • Update HTTPS-Everywhere to 5.2.17
    • Update NoScript to 5.0.5
    • Update Go to 1.8.3 (bug 22398)
    • Bug 21962: Fix crash on about:addons page
    • Bug 21766: Fix crash when the external application helper dialog is invoked
    • Bug 21886: Download is stalled in non-e10s mode
    • Bug 21778: Canvas prompt is not shown in Tor Browser based on ESR52
    • Bug 21569: Add first-party domain to Permissions key
    • Bug 22165: Don't allow collection of local IP addresses
    • Bug 13017: Work around audio fingerprinting by disabling the Web Audio API
    • Bug 10286: Disable Touch API and add fingerprinting resistance as fallback
    • Bug 13612: Disable Social API
    • Bug 10283: Disable SpeechSynthesis API
    • Bug 22333: Disable WebGL2 API for now
    • Bug 21861: Disable additional mDNS code to avoid proxy bypasses
    • Bug 21684: Don't expose navigator.AddonManager to content
    • Bug 21431: Clean-up system extensions shipped in Firefox 52
    • Bug 22320: Use preference name 'referer.hideOnionSource' everywhere
    • Bug 16285: Don't ship ClearKey EME system and update EME preferences
    • Bug 21675: Spoof window.navigator.hardwareConcurrency
    • Bug 21792: Suppress MediaError.message
    • Bug 16337: Round times exposed by Animation API to nearest 100ms
    • Bug 21972: about:support is partially broken
    • Bug 21726: Keep Graphite support disabled
    • Bug 21323: Enable Mixed Content Blocking
    • Bug 21685: Disable remote new tab pages
    • Bug 21790: Disable captive portal detection
    • Bug 21686: Disable Microsoft Family Safety support
    • Bug 22073: Make sure Mozilla's experiments are disabled
    • Bug 21683: Disable newly added Safebrowsing capabilities
    • Bug 22071: Disable Kinto-based blocklist update mechanism
    • Bug 22415: Fix format error in our pipeline patch
    • Bug 22072: Hide TLS error reporting checkbox
    • Bug 20761: Don't ignore additional SocksPorts
    • Bug 21862: Rip out potentially unsafe Rust code
    • Bug 16485: Improve about:cache page
    • Bug 22462: Backport of patch for bug 1329521 to fix assertion failure
    • Bug 21340: Identify and backport new patches from Firefox
    • Bug 22153: Fix broken feeds on higher security levels
    • Bug 22025: Fix broken certificate error pages on higher security levels
    • Bug 21887: Fix broken error pages on higher security levels
    • Bug 22458: Fix broken `about:cache` page on higher security levels
    • Bug 21876: Enable e10s by default on all supported platforms
    • Bug 21876: Always use esr policies for e10s
    • Bug 20905: Fix resizing issues after moving to a direct Firefox patch
    • Bug 21875: Modal dialogs are maximized in ESR52 nightly builds
    • Bug 21885: SVG is not disabled in Tor Browser based on ESR52
    • Bug 17334: Hide Referer when leaving a .onion domain (improved patch)
    • Bug 18531: Uncaught exception when opening ip-check.info
    • Bug 18574: Uncaught exception when clicking items in Library
    • Bug 22327: Isolate Page Info media previews to first party domain
    • Bug 22452: Isolate tab list menuitem favicons to first party domain
    • Bug 15555: View-source requests are not isolated by first party domain
    • Bug 3246: Double-key cookies
    • Bug 8842: Fix XML parsing error
    • Bug 5293: Neuter fingerprinting with Battery API
    • Bug 16886: 16886: "Add-on compatibility check dialog" contains Firefox logo
    • Bug 19645: TBB zooms text when resizing browser window
    • Bug 19192: Untrust Blue Coat CA
    • Bug 19955: Avoid confusing warning that favicon load request got cancelled
    • Bug 20005: Backport fixes for memory leaks investigation
    • Bug 20755: ltn.com.tw is broken in Tor Browser
    • Bug 21896: Commenting on website is broken due to CAPTCHA not being displayed
    • Bug 20680: Rebase Tor Browser patches to 52 ESR
    • Bug 22429: Add IPv6 address for Lisbeth:443 obfs4 bridge
    • Bug 22468: Add default obfs4 bridges frosty and dragon
  • Windows
    • Bug 22419: Prevent access to file://
    • Bug 12426: Make use of HeapEnableTerminationOnCorruption
    • Bug 19316: Make sure our Windows updates can deal with the SSE2 requirement
    • Bug 21868: Fix build bustage with FIREFOX_52_0_2esr_RELEASE for Windows
  • OS X
    • Bug 21940: Don't allow privilege escalation during update
    • Bug 22044: Fix broken default search engine on macOS
    • Bug 21879: Use our default bookmarks on OSX
    • Bug 21779: Non-admin users can't access Tor Browser on macOS
    • Bug 21723: Fix inconsistent generation of MOZ_MACBUNDLE_ID
    • Bug 21724: Make Firefox and Tor Browser distinct macOS apps
    • Bug 21931: Backport OSX SetupMacCommandLine updater fixes
    • Bug 15910: Don't download GMPs via the local fallback
  • Linux
    • Bug 16285: Remove ClearKey related library stripping
    • Bug 22041: Fix update error during update to 7.0a3
    • Bug 22238: Fix use of hardened wrapper for Firefox build
    • Bug 21907: Fix runtime error on CentOS 6
    • Bug 15910: Don't download GMPs via the local fallback
  • Android
    • Bug 19078: Disable RtspMediaResource stuff in Orfox
  • Build system
    • Windows
      • Bug 21837: Fix reproducibility of accessibility code for Windows
      • Bug 21240: Create patches to fix mingw-w64 compilation of Firefox ESR 52
      • Bug 21904: Bump mingw-w64 commit to help with sandbox compilation
      • Bug 18831: Use own Yasm for Firefox cross-compilation
    • OS X
      • Bug 21328: Updating to clang 3.8.0
      • Bug 21754: Remove old GCC toolchain and macOS SDK
      • Bug 19783: Remove unused macOS helper scripts
      • Bug 10369: Don't use old GCC toolchain anymore for utils
      • Bug 21753: Replace our old GCC toolchain in PT descriptor
      • Bug 18530: ESR52 based Tor Browser only runs on macOS 10.9+
      • Bug 22328: Remove clang PIE wrappers
    • Linux
      • Bug 21930: NSS libraries are missing from mar-tools archive
      • Bug 21239: Adapt Linux Firefox descriptor to ESR52 (use GTK2)
      • Bug 21960: Linux bundles based on ESR 52 are not reproducible anymore
      • Bug 21629: Fix broken ASan builds when switching to ESR 52
      • Bug 22444: Use hardening-wrapper when building GCC
      • Bug 22361: Fix hardening of libraries built in linux/gitian-utils.yml

Comments

Please note that the comment area below has been archived.

test (not verified) said:

June 07, 2017

Permalink

Today is 7th of July but I still cannot see new tor version in official tor repository for Debian. Issue with ALSA is very sad, too sad. Pulseaudio, like systemd, are the things which were always avoided on system-critical OSes.

test (not verified) said:

June 07, 2017

Permalink

When I open youtube popup says me that I must install pulseaudio to het sound working, button with help redirects me on the page: link. However, there is no this page. You should fix the link.

P.S. Preview in commenting in tor-blog with enabled JS is not working. It doesn't show formatted text, only its source.

We ship Tor Browser with

pref("browser.reader.detectedFirstArticle", true);
pref("reader.parse-on-load.enabled", false);

to reduce fingerprinting surface. Does it help if you flip both preferences on the about:config page?

merlin (not verified) said:

June 07, 2017

Permalink

The article mentions:

In addition to that, Linux and macOS users have the option to further harden their Tor Browser setup by using only Unix Domain sockets for communication with tor.

How can I enable this?

1. Open about:config in a browser window.
2. Toggle the following two preferences so that their value becomes true:
extensions.torlauncher.control_port_use_ipc
extensions.torlauncher.socks_port_use_ipc
3. Restart Tor Browser.

arma

arma said:

June 07, 2017

Permalink

That sounds like a great step -- making Tor Browser use unix domain sockets, not tcp sockets, when interacting with Tor.

But does it actually harden Tor Browser in any way? That is, is there something fundamentally safer about using unix domain sockets vs tcp? I would guess that the security would come from the step after that, which would be "and then we prevent Tor Browser from making any tcp connections"?

yawning

yawning said:

June 07, 2017

Permalink

> But does it actually harden Tor Browser in any way?

No. So the blog post is misleading at best.

> I would guess that the security would come from the step after that, which would be "and then we prevent Tor Browser from making any tcp connections"?

Yes.

Use the sandbox.

merlin (not verified) said:

June 07, 2017

Permalink

Yes, it's making it harder to bypass Tor. The Browser process won't be able to send network package that don't go through Tor. This is a good additional safety net to avoid leaking your real IP. Also, at some point, seccomp could be used to block some of the network related system calls reducing the attack surface.

Sorry, but I think this is incorrect.

Having your Tor Browser use the unix domain sockets to talk to Tor is not what prevents your Tor Browser process from sending network packets that don't go through Tor.

Step one is to have your Tor Browser use unix domain sockets to talk to Tor, and step two is sandboxing your Tor Browser so it can't talk to anything else in any other way. You have to do both steps.

See also
https://decvnxytmk.oedi.net/projects/torbrowser.html.en#downloads-sandbox

Anonymous (not verified) said:

June 08, 2017

Permalink

jep, and block network access could be done by just adding one or two line in the apparmor profile or in firejail (yawning sandbox might be the better solution but unfortunately it's not available for 32bit Systems)

Anonymous (not verified) said:

June 10, 2017

Permalink

That's nice, but how do we INSTALL sandboxed-tor-browser?
I've not been able to find instructions anywhere, and none come with the zip file I downloaded from your provided link. Just un-zipping and clicking on the file seems to do nothing.
I'm using Ubuntu 16.04 LTS 64-bit.

Anonymous (not verified) said:

June 07, 2017

Permalink

Thank guys, great job!

Quite often when I opened Tor Browser, there was a warning sign of a yellow triangle with an exclamation mark in the "Open Settings" button on the connecting dialog box. When clicking on that, it showed a "Copy to clipboard" button.

May anyone tell me a little bit about this warning? I'm wondering if my connection was compromised and no longer anonymous in these cases. This time, for example, the content I got from the "Copy to clipboard" was:

06/07/2017 12:58:58.500 [NOTICE] Bootstrapped 5%: Connecting to directory server
06/07/2017 12:58:58.500 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
06/07/2017 12:58:59.200 [WARN] Proxy Client: unable to connect to 68.45.52.117:40365 ("general SOCKS server failure")
06/07/2017 12:59:00.100 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
06/07/2017 12:59:00.100 [WARN] Proxy Client: unable to connect to 68.45.52.117:40365 ("general SOCKS server failure")
06/07/2017 12:59:00.300 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
06/07/2017 12:59:01.200 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
06/07/2017 12:59:08.900 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
06/07/2017 12:59:08.900 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit
06/07/2017 12:59:10.100 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
06/07/2017 12:59:10.100 [NOTICE] Bootstrapped 100%: Done
06/07/2017 12:59:11.600 [NOTICE] New control connection opened from 127.0.0.1.
06/07/2017 12:59:11.700 [NOTICE] New control connection opened from 127.0.0.1.
06/07/2017 13:00:18.400 [WARN] Proxy Client: unable to connect to 178.62.29.226:9443 ("general SOCKS server failure")
06/07/2017 13:00:19.700 [WARN] Proxy Client: unable to connect to 178.62.29.226:9443 ("general SOCKS server failure")
06/07/2017 13:00:19.800 [NOTICE] new bridge descriptor 'Unnamed' (fresh): $958ACD25DACDDE1CF6FE463FBFA28BFEB8BFF82B~Unnamed at 194.132.209.61
06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 108.61.191.37:9443 ("general SOCKS server failure")
06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 5.35.86.79:39563 ("general SOCKS server failure")
06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 35.185.60.254:9443 ("general SOCKS server failure")
06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 139.59.147.112:36715 ("general SOCKS server failure")
06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 104.153.209.217:25447 ("general SOCKS server failure")
06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 185.163.45.19:57339 ("general SOCKS server failure")

Those lines look to me like you configured your Tor Browser to use bridges (most likely a pluggable transport like obfs4), and some of your bridges are down.

If you don't need bridges, you'll probably get a faster and smoother experience by not using them. You can change your settings by clicking on the green onion and choosing network settings and then unclicking things.

Anonymous (not verified) said:

June 08, 2017

Permalink

Sorry for slowing in reply, arma, there are a lot of so important things happen these few days! I was busy stalking Jame B. Comey around the Senate floor and hunting for the Britain election outcome! xD

I can also guess that the bridges might down, but wonder is that did that (the warning) mean my connection would be compromised and no longer safe and anonymous??

I know the speed and smoothness of the connection using bridges may not that of the best choice. I hadn't need bridges until the warning appeared more and more frequently for me that using bridges may be my best choice. There were days all the other methods (obfs4, obfs3,... without bridges) gave me the warning sign.

Anonymous (not verified) said:

June 08, 2017

Permalink

Uhmm... the warning sign of a yellow triangle with an exclamation marked in the "Open Settings" button on the connecting dialog box. I have been talking all about this sign!

I just wanna make it clear that did that sign mean the connection in those cases might be compromised and no longer safe and anonymous. I have been wondering all about that!

I thought you might have meant that.

The yellow blinking triangle means that there's a Tor Browser update available, and you should move to the newer version. You can do that by clicking on the green onion and asking to update.

It has nothing to do with "your circuits are suddenly no longer safe".

Anonymous (not verified) said:

June 09, 2017

Permalink

OMG! Are you kidding me??

It's not the blinking triangle on the onion icon on the top-left corner of the Tor Browser to notify new version available! That sign will disappear once I update to the newest version, which I always do.

It's a yellow triangle with an exclamation marked in the "Open Settings" button on the connecting dialog box, the small dialog box which appears every time we launch Tor Browser! If clicking on the "Open Settings" with the warning triangle on it, there will be a "Copy to clipboard" button to get the message log one of which I posted earlier! I'm wondering if the connection in those cases might be compromised and no longer safe and anonymous.

I think many people would meet this issue already, because I have got it pretty frequently.

I get the same warning if my internet connection is running a bit slow. Try connecting during off peek hours or maybe take a close look at your internet setup, maybe a router modem reboot?.?.?

Hmm... ok, amar, I will understand nobody has the answer for my question, or...

"If you love your answer, you can keep your answer; if you love your plans, you can keep your plans too!" xD

Anonymous (not verified) said:

June 12, 2017

Permalink

Thank you very much, arma, gk, and Lee!

Especially gk, that's exactly what I have been looking for. I could only guess that (1) some bridges might down, (2) the connections were probably NOT compromised -- since in that case I suppose Tor would terminate the connections for the most security possible and I would not be able to access Internet. I actually never access Internet in those cases either -- also, for the most security possible, but I still want the answer, so thank gk one more time.

@Lee: No, that warning has been appearing very randomly, there has been no regular pattern like slow connectivity or peak hours for me to notify (it can appear at any time).

Anonymous (not verified) said:

June 08, 2017

Permalink

Something like roll-out period for new ESR to fix new bugs w/o waiting next 6 weeks? Neat.

_John (not verified) said:

June 07, 2017

Permalink

If you are using Add-ons with filter lists in Tor Browser 7.0, for example uBlock Origin, Adblock Plus etc. ,it takes extremely long to start the browser
In Tor Browser 6.5 and previous this was not really an issue. It was only a small delay barely noticeable.
This problem is new to version 7.0. I hope you can look into that.

How to reproduce:
- Use a newely installed Tor Browser v. 7.0
- Install uBlock Origin
- See how the browser will freeze for some seconds.
- Restart the Browser and see how it will take extremely long to startup

James Edward L… (not verified) said:

June 07, 2017

Permalink

I'm still hoping for 64-bit versions of Tor and the Tor Browser for Windows; maybe they'll show up alongside the ESR59-based Tor Browser, because Firefox 53+ no longer supports Vista, and most installations of Windows 7+ are 64-bit, so they will be able to benefit from 64-bit software.

We'll hope to have 64bit Windows versions in our alpha series later this year. And, yes, assuming all is going well they will be available in the stable series with Tor Browser based on Firefox 59.

Yes, we are sorry about that but Mozilla raised the minimum requirements for Firefox 52 to 10.9. Technically we could work around that and provide Tor Browser for 10.7 users as well but the risk introducing weird issues that way is too high.

I agree. some of us still want/need to be able to use Tor browser on older machines, it'd be very helpful to have a blog post specifically about this issue and possible ways to continue using tor with a browser reliably on such machines.

SB (not verified) said:

June 07, 2017

Permalink

my system is not supported.. meanwhile what can I do? updating only TOR instead of tor browser, but how do it?
help please :D

I think it's actually considered a feature. The goal of the 'new identity' button is to make your future activities unlinkable to your past activities. One potential way to link them is to look at window size. So whatever your window size was before, Tor makes sure to normalize it to the default after.

Anonymous (not verified) said:

June 07, 2017

Permalink

I think it was done by mistake. If the point was to reset the resolution, wouldn't the resolution just be set to default instead of closing everything? Or is isolation broken between tabs so that all tabs really have to be closed?

We have had issues in the past about state not being deleted if we don't close the browser window. New Identity means "clean slate" and not just "default window size", so as arma said this is a feature.

Anonymous (not verified) said:

June 08, 2017

Permalink

I know, arma, the difference between "new identity" and "new Tor Circuit..." but this is a different window behavior under Linux.
I try to explain better:
-Tor Browser until previous version
you select "new identity" and Tor Browser windows switch fast giving you a clean Tor Browser
-This version of Tor Browser
you select "new identity" and Tor Browser opens a new window ( under Linux is in a different position of the screen ) and THEN close the old one ( this is why under Linux it opens in a new portion of the screen ).

Just try ten times with the previous version of Tor Browser and the the new one.
Hope it's clear now. ;)

marine (not verified) said:

June 07, 2017

Permalink

Hi there, I wanted to report that Avast detects an idp.generic infection for Tor on Windows since this update. Saw an identical report in comments of release 4.0.8. Do you still advise to add Tor to exceptions as a workaround?

myname (not verified) said:

June 07, 2017

Permalink

Nice to see that you listened on the referrer problem. Please make the following preferences as default in the next release:
network.http.referer.trimmingPolicy;2
network.http.sendRefererHeader;1
network.http.referer.spoofSource;true

These would be a huge improvement and should not cause any problems.

Errorreporting (not verified) said:

June 07, 2017

Permalink

After installing 7.0, bitdefender detected pluggabletransports\meek-client.exe as a virus, Gen:Variant.Graftor.

Anonymous (not verified) said:

June 08, 2017

Permalink

The main thing that worries me is

if a navigation from an encrypted to a non-encrypted part of the same site (i.e. sharing the same cookies) happens in the same tab, NoScript removes its ";Secure" patch to ensure compatibility

, which means it gives away your private cookies with fake requests from bad exits.

Anonymous (not verified) said:

June 07, 2017

Permalink

TBB 7.0 gets stuck in some sort of refresh-loop when trying to post here with the security slider set to "high security". This could lead to accidental DDoS as well as people setting dangerous security levels to get around the refresh bug. 6.5.2 also had this problem.

yawning

yawning said:

June 07, 2017

Permalink

> IE does Tor Browser Sandbox use Unix Socket Domains by default?

The sandbox has always used AF_LOCAL sockets, and has never had support for anything else.

I have no idea wtf they were thinking putting that blurb in the blog post since on it's own that feature adds zero to security.

Actually, it is pretty weird that this is working for you. The problem is that we are using Firefox's Private Browsing Mode by default and that IndexedDB is *not* supported in it yet, see: https://bugzilla.mozilla.org/show_bug.cgi?id=781982. So, even if you flipped the preference to "true" that should not make IndexedDB available in an unmodified Tor Browser.

ollieparanoid (not verified) said:

June 14, 2017

Permalink

I had private browsing mode by default turned off in my tor browser config, because I run it as default browser and I like to keep the history around (with additional security measures, such as an encrypted disk etc.).

That is probably, why it works.

plshlpthx (not verified) said:

June 07, 2017

Permalink

Is there a way to revert back to the previous version? This update is severely messing with a few websites that i frequent.

Agreed, not only a few websites, the used Firefox version is a mess in itself.
The https passowrd box warning does not make sense in tor.
The removed css styling of elements makes most websites look ugly.

esr52 wtf? even the browser error pages have errors!
copy-paste from the error page source (page is not shown complete!)

I second the request for a possibility to revert bck to the previous version.

Cort (not verified) said:

June 08, 2017

Permalink

This one
Bug 21887: Fix broken error pages on higher security levels
is NOT fixed, happens periodically and is quite annoying because if it was a form page before you cant get the resend button anymore and loose all your input data.

Anonymous (not verified) said:

June 07, 2017

Permalink

"Android

Bug 19078: Disable RtspMediaResource stuff in Orfox"
Thank you for the excellent work! Please, could you post the update to F-Droid, since not everyone uses Google Play?
F-Droid isn't perfect but at least it doesn't have a developer backdoor like Google Play does that can uninstall your firewall and install spyware...

We are not responsible yet for Orfox but I think the Guardianproject is aware of it and I hope they post an updated Orfox version soon.

endry (not verified) said:

June 07, 2017

Permalink

tor It does not connect and I do not know where to write, it happened right after the update, here are the logs, the piece:
08.06.2017 6:48:39.800 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
08.06.2017 6:48:39.800 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
08.06.2017 6:48:41.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:48:44.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:48:44.800 [WARN] Application request to port 23: this port is commonly used for unencrypted protocols. Please make sure you don't send anything you would mind the rest of the Internet reading!
08.06.2017 6:48:44.800 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
08.06.2017 6:48:44.800 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
08.06.2017 6:48:44.800 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
08.06.2017 6:48:47.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:48:50.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:48:53.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:48:56.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:48:59.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:02.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:05.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:08.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:10.800 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
08.06.2017 6:49:11.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:14.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:17.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:20.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:23.800 [WARN] socks5: command 3 not recognized. Rejecting.
08.06.2017 6:49:23.900 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
08.06.2017 6:49:23.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
08.06.2017 6:49:23.900 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
08.06.2017 6:49:24.200 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Wow. You seem to have some sort of really broken application that you're trying to shove through Tor?

And also you configured your Tor Browser to use bridges, but those bridges are down or something? Or maybe you weren't on the Internet while these logs happened?

Anonymous (not verified) said:

June 07, 2017

Permalink

Good job. One thing though. I have the newest 7.0. But can not post here normally. I have to lower the security slider first. Is this problem in the new blog, or in Tor Browser?

Anonymous (not verified) said:

June 07, 2017

Permalink

little bit offtopic:

your new site-design is really 'confusing'. It looks like a FLOODING.

With the old design you have fast overall view when you look to the new things in new TBB version.
With the new design you are looking, looking, looking, looking ..... -a really confusing design?
Or do you have a gigantic monitor?

Biep (not verified) said:

June 07, 2017

Permalink

I am in China, and used to have a set of custom meek bridges, but having those leads to errors under 7.0. Even having them, but selecting "Connect with provided bridged" - meek-azure causes start-up to fail: I must completely clear the "enter custom bridges" field. This seems a bug to me.

Biep (not verified) said:

June 12, 2017

Permalink

Hmm - it seems the problem just spontaneously disappeared. I copied the custom bridges back in, but selected "provided bridges" and meek-azure, and did a restart. That worked - but the bridges I had copied in were gone (I hate that, BTW).

Then I copied them in again, and kept the selection of "custom bridges", and restarted again - and it worked quickly and flawlessly.

Sorry for this..

Anonymous (not verified) said:

June 08, 2017

Permalink

After upgrade to v7, when I tried to login to my email which hosted on Hidden service:

HTTP: Your connection is not secure

Ugh, can't you ignore all security alert if HOST is .onion?

Anonymous (not verified) said:

June 07, 2017

Permalink

Question:

there is a long automatic chosen relay list in the state-file, e.g
"Guard in=default rsa_id=xxxxxxxxxxxxxxxxxxx nickname=xxxxxxxxxxxxxx sampled_on=2017-05-29T19:39:55 sampled_by=0.3.0.7 listed=1

Guard in=default rsa_id=xxxxxxxxxxxxxxxxxxx nickname=xxxxxxxxxxxxxxxxxxx sampled_on=2017-05-30T17:00:39 sampled_by=0.3.0.7 listed=1"

Non-Guardrelays, too. Can you explain?

Anonymous (not verified) said:

June 08, 2017

Permalink

I'm also seeing failed connection attempts with bridgedb and the default obfs4 bridges. Both are spamming "Ignoring directory request, since no bridge nodes available yet." notices.

I managed to connect after a few tries. Could this be the new guard selection? The same bridgedb bridges used to work on the first try. I haven't used the 0.3.0.x series, so I really couldn't tell.

Hm, I just tested with a clean Tor Browser and I got something like

Jun 08 08:25:00.000 [notice] I learned some more directory information, but not enough to build a circuit: We're missing descriptors for some of our primary entry guards
Jun 08 08:25:00.000 [notice] Ignoring directory request, since no bridge nodes are available yet.

But connecting continued and succeeded. Are you saying that there is a connection for you between this spamming and failed connection attempts?

Anonymous (not verified) said:

June 08, 2017

Permalink

Correct, and I also tested with a clean tor-browser. I should have kept the logs, but when the connections failed the initial setup just hanged, when trying with the bridgedb bridges usually at 75%. I left it for a few minutes, but nothing happened. I also got unable to connect warnings, which is odd because I know they just worked.

I should mention, when the connection succeeds I might also get some notices, however, not nearly as many.

test (not verified) said:

June 08, 2017

Permalink

I'm experienced Linux user. I use TBB in my Xen PV DomU. It worked fine before this release. I use Sys-V startup system for Debian and on-the-fly sound card PCI passthrough. Everything worked. Now I spent few hours to get PulseAudio working on my VM, but failed. Finally, I got it running, but without sound working. So, unfortunately, I have to continue to use my old TBB for sound-critical cites such as youtube. I hope you (and Mozilla) will hear our voices and recompile TBB with ALSA support.

Another issue follows from the previous fact. If I run TBB 7.0 without PulseAudio, it spams me with banner popup asking to install it. Every time some sound even happen at the same page, popup is shown again. It is too annoying.

Another thing I noticed is browser has become slower. When I scroll page I experience interrupts. The same happens when I type text in browser. Its behavior looks like 100% processor usage or out of RAM problem. 7.0 release it too raw.

cssanon (not verified) said:

June 08, 2017

Permalink

The update killed use of CSS for me (online and localized). It was buggy before and I ignored it but now it seems to be completely broken.
Any way to restore it or should I simply go back to TOR's last version.?

What do you mean with "killed use of CSS for me (online and localized)"? Does that happen with Firefox 52 ESR as well? Or is that a Tor Browser issue? If the latter what are steps to reproduce it?

cssanon (not verified) said:

June 08, 2017

Permalink

I didn't use Mozilla's browser recently but after installing it seems you're right. It's a problem with the Firefox browser (52, 53). Sorry to bother you.

(Localized meant, I used a CSS file stored on my PC. I thought it's a NoScript issue, at first.)

boby (not verified) said:

June 08, 2017

Permalink

I updated Tor Browser to 7.0 and I still see (it was already in previous versions) in tor button Security Setting to level High the following text:

Javascript is disabled by default on all sites.
On sites where JavaScript is enabled [...]

Confusing! Is JavaScript DISABLED ON ALL SITES or not?

Darrin (not verified) said:

June 08, 2017

Permalink

getting an error message when i download Tor. 0x000005. Any reason for that? is it my antivirus or defender perhaps?

It could be related to your antivirus or firewall.

It's not much to go on though. What is giving you the error? What are you using to download Tor Browser? What do you do that gives you the error?

Anonymous (not verified) said:

June 08, 2017

Permalink 

  1. 19:58:40.828 An error occurred during a connection to <a href="http://www.google.com:443.
  2.  
  3. The" rel="nofollow">www.google.com:443.</a></p>
  4. <p>The client has encountered bad data from the server.</p>
  5. <p>Error code: <a id="errorCode" title="SSL_ERROR_BAD_SERVER">SSL_ERROR_BAD_SERVER</a><br />
  6.  1 (unknown)<br />

Bad server! Internet doesn't lie ;-)))

Alex (not verified) said:

June 08, 2017

Permalink

It was working fine yesterday, when I performed the automatic update from version 6 to version 7. Now it shows only a blank screen on every site. No, I don't mean those hidden .onion site, but literally EVERY site, including the torproject website. The browser shows the page title, the favicon, but the screen remains white. Basically, this version has become a load of useless bytes on my hard disk. Working on a Debian 8 PC.

Does it work if you start over with a clean new Tor Browser 7? Do you get some hints on what is going wrong in your terminal if you start Tor Browser with ./start-tor-browser.desktop --debug in your Tor Browser directory?

anonimos (not verified) said:

June 08, 2017

Permalink

Manjaro pamac found the update and asked to upgrade my tor browser, so I said yes. When it was done I started and all my bookmarks and settings were not there as it was the first time I ever run it.
I expect such behavior should come with a warning to allow us to back things up before they vanish. This is not the first time this happens, and it was under a different linux distribution that it had happened.

The responses for how to update to the new tor and where would it be found as source or binary have been non-existing. What's going on?

Is "Manjaro pamac" some sort of package manager?

It sounds like you did not install Tor Browser.

Maybe you installed something like the third-party tool "torbrowser-launcher" instead? if so, that third-party tool is probably where you should be filing your tickets (and/or maybe you should be using Tor Browser the normal default way).

Дмитро (not verified) said:

June 08, 2017

Permalink

I ask the distinguished as a chain torus. How to be sure that the chain? I want my browser torus transmits, not just uses, but how to check for sure? If possible, write off in detail.

Anonymous (not verified) said:

June 08, 2017

Permalink

Oh shi*

  1. 21:32:23.162 uncaught exception: out of memory 1 (unknown)<br />

Me too.
ip-check.info shows browser authentication highlighted in red, with a unique ID number.
The description says it is as bad for privacy/security as third party cookies.
My previous version did not do this, and was highlighted in green, indicating a setting.
This changed after the automatic update to 7.0.

Anonymous (not verified) said:

June 10, 2017

Permalink

Previously, when running the test, two popup authentication-type windows would come up first, which had text instructing the user to click "cancel". Now, those windows do not come up. I understand that they have something to do with testing the browser authentication.

If their test has not changed, then why would these two popup windows no longer appear?

Anonymous (not verified) said:

June 08, 2017

Permalink

Could you make it easier to find the PGP keys used to sign the various releases? It's nice that you provide PGP-detached signature file, but you can't verify the signature without the PGP key.

Tommy (not verified) said:

June 08, 2017

Permalink

32-bit Tor BB 7.0 for linux does not work when run in a chroot. The browser starts, but does not display loaded web pages, ie. displays a blank page. Previous versions worked perfectly.

Running the 64-bit version natively works fine.

Anonymous (not verified) said:

June 08, 2017

Permalink

Testing Tor Browser 7.0 on the ip-check.info website, it shows a unique browser authentication and is highlighted in red as a severe privacy threat. My old Tor Browser did not, and was green.

Any suggestions?

toruser39284 (not verified) said:

June 08, 2017

Permalink

Since the update, Tor does not save my adjustment to the network setting and about:config, meaning I have to re-do at each browser launch. Anyone have any idea what happened?

Torguy (not verified) said:

June 09, 2017

Permalink

I’m just using the Tor browser without the Tor network by going into network settings and selecting “No Proxy”. Then in “about:config” going to “network.proxy.socks_remote_dns” and Toggling.

The next step is to toggle "extensions.torlauncher.start_tor”, which for some reason does save in-between browsing sessions. Since the update, the steps mentioned above do not save and I have to re-do each browsing session.

anon (not verified) said:

June 09, 2017

Permalink

Thanks. I know VPNs have major issues with this but I'm wondering how Tor is different to VPNs?

Anonymous (not verified) said:

June 09, 2017

Permalink

Yet another quite annoying change:
If I right click on a link, the popup menu
is positioned below the cursor, so immediately
releasing the button activates the Open in new
window menu, which is not even the first.
Earlier the menu was a little bit to the right,
so after right clicking I could move my mouse
calmly to a menu item, and could choose it
with a left click. Now I have to drag.

Charizard (not verified) said:

June 09, 2017

Permalink

New version is causing overlapping items on the YouTube website like the video control / play button and the masthead to flicker (macOS).

Anon0 (not verified) said:

June 09, 2017

Permalink

I sometimes wondered to myself if Tor devs would be that dumb to auto update Tor Browser to a version no longer compatible with the operating system itself. Well done. You were that stupid.

Did it not occur to you that it would have been better NOT to have updated if: System OS X version < new minimum and maybe displayed a warning message ? It's so obvious. But to just disable software that way, that people rely on causes a whole lot of inconvenience. Stupid, stupid, stupid.

FWIW, this is fixed now. You should be able to use 6.5.2 again without getting any updates and it is still up-to-date for the next two days until we finally switch to ESR52. Sorry for the inconvenience.

Anonymous (not verified) said:

June 09, 2017

Permalink

Cert for this page, vbdvexcmqi.oedi.net has no mention of torproject.org domain.
Only:
5667908084563968-fe2.pantheonsite.io

?

Anonymous (not verified) said:

June 09, 2017

Permalink

When 1 TBB browserwindow is open, i see 2 firefox.exe*32 with 2 different PIDs.
That's new.
What's the reason for?

bopper (not verified) said:

June 09, 2017

Permalink

Is the documentation on gpg key validation that the torbrowser presents valid?

I tried verifying a key and it did not work

gpg --keyserver pool.sks-keyservers.net --recv-keys 0x4E2C6E8793298290
gpg: keyring `/home/macneal/.gnupg/secring.gpg' created
gpg: requesting key 93298290 from hkp server pool.sks-keyservers.net
?: pool.sks-keyservers.net: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Connection timed out
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver unreachable
gpg: keyserver communications error: public key not found
gpg: keyserver receive failed: public key not found
macneal@RALF2:~/Downloads$ gpg --fingerprint 0x4E2C6E8793298290
gpg: error reading key: public key not found

CYBER SECURITY (not verified) said:

June 10, 2017

Permalink

We love TOR and as a security team we do appreciate it. How ever more journalists are using it world wide for fear of abductions. We salute them for their stories.. Please use Linux any version to help freedom and democracy
around globe. Thanks a lot to democracynow.org

anonymous (not verified) said:

June 10, 2017

Permalink

How would someone know if the new machine they're buying is SSE2-capable?

On Windows Tor Browser 7.0 won't run on non-SSE2 capable machines anymore.

Unless the new machine is using an exotic embedded x86 processor, or predates either the Pentium 4 (2000) or Athlon 64 (2003) it will support SSE2. If it can run a 64 bit operating system, it also will support SSE2, because the extension is a mandatory part of x86_64.

anonymous (not verified) said:

June 10, 2017

Permalink

Thank you. So with Windows, basically anything 32-bit and 64-bit Vista to 10? I'm trying to refurbish an extra Vista 32-bit and it's working fine.

toruser (not verified) said:

June 10, 2017

Permalink

Tor Browser 7.0 problem: No matter how many times I click on "new tor circuit" the first node in the network remain the same. only the 2nd and 3rd nodes change.
What's up with this?
I deleted and reinstalled several times but the problem persists.

me (not verified) said:

June 10, 2017

Permalink

yes, thanks to cia for this new tor version, since cia added a lot of tor server relay to spy users, tor doesn't have the option to easily made your installation of tor becoming a relay !!

Anon (not verified) said:

June 10, 2017

Permalink

I have downloaded and installed this version at least a dozen times. I keep getting the error "Could not connect to Tor control port."

I have made sure I am not using any bridges. I have checked there are no firewall problems.

I am using Windows 7 Enterprise.

Any assistance is appreciated.

Do you have some antivirus software installed? If so you can uninstall it and your firewall software for testing purposes (disabling is often not enough). We hear this issue quite often if we ship a new Tor version which is usually caused by antivirus/firewall software being wrong in "thinking" this new Tor version is malicious.

Teller (not verified) said:

June 10, 2017

Permalink

From the IP address 192.82.150.249 they are able to block OBFS4,OBFS3 meek-amazon. This site is a Canadian public WIFI site used in City Brampton.

bolt (not verified) said:

June 10, 2017

Permalink

Does the new version works simultaneously in the browser and as a socks proxy? I have it working this way, using "SocksPort" in a torrc config file.

What happened with the "ControlPort" parameter? Tor no longer accepts it. And when "SocksPort" enabled, is control port always 9151? (i have it working). How to change control port now?

"ExitNodes" parameters act the same as before, if interesting.

Tor Launcher is now responsible for setting the proper parameters for the default socks and control port. For the latter there is a preference now, extensions.torlauncher.control_port, which you might help you. Plus there are environment variable you could set: TOR_CONTROL_HOST and TOR_CONTROL_PORT.

Nicola (not verified) said:

June 11, 2017

Permalink

ip-check.info
suddenly states (differing from Tor Browser 6.5.2):
"You are using Tor, but your browser profile differs from the recommended `Tor Browser Bundle` default profile."
Furthermore, "Authentication" and "User-Agent" now show up as red on both Tor Browser 7.0 for Windows and Linux 64-bit, others we have not checked.

Viktor (not verified) said:

June 11, 2017

Permalink

ТОР не работает На OS X Макбук. Окно выскакивает с надписью: "надо обновиться до версии 10.9"

7.0 does not work! (not verified) said:

June 11, 2017

Permalink

Just upgraded from 6.5.1 to 7.0 (on win10 64) and Tor does not even start. Rebooted PC still nothing. Until 10 min ago 6.5.1 worked perfectly. Luckily I still have the 6.5.1 exe file, so got rid of 7.0 reinstalled 6.5.1 and it works fine...

Do you have an antivirus/firewall program on your computer? If so, you could uninstall it and see if that solves the problem (disabling is often not enough). We see this issue often if we ship new Tor versions which is caused by antivirus/firewall software "thinking" this new Tor version is harmful (which it is not).

David (not verified) said:

June 13, 2017

Permalink

same issue, error persists, and it doesnt copy a log, tried without the firewall and the antivirus same error, should i return to the older version?

Rocky (not verified) said:

June 13, 2017

Permalink

Why does TB 7.0 need access to:

/dev/shm/org.chromium.* rw,
@{PROC}/[0-9]*/net/route r,
@{PROC}/[0-9]*/net/arp r,

Anonymous (not verified) said:

June 13, 2017

Permalink

I run torbrowser in chrooted environment (CentOS 6.5). After upgrade to version 7.0 torbrowser doesn't render content of html pages. Only titles are shown, but white space instead of text and pictures in the main area. The following messages are displayed in the terminal

Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 1000, 800 (t=6.19759) [GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 1000, 800

When torbrowser is running in normal environment it works correctly. However I prefer to run it in chrooted (restricted) environment for better security. It's been working nice for the last several years until now. What can be the cause of this issue?

Anonymous (not verified) said:

June 14, 2017

Permalink

There are two firefox versions available on you link. Firefox 45.9.0 ESR works in my environment. Firefox 52.2.0 ESR doesn't work even in normal environment because requires new GTK 3 that isn't provided with CentOS 6.5 packet management. So it involves compiling GTK and dependencies from source. Maybe I will do it later and then comment it here.

Anonymous (not verified) said:

June 17, 2017

Permalink

It's quite easy if chroot to root directory '/'.

I figured out the cause of the issue. Version 7 of torbrowser requires filesystem /dev/shm. So adding it to chroot directory resolves the problem. Thanks for your attention.

AAA (not verified) said:

June 13, 2017

Permalink

Tor Browser 7.0 won't start! When I try to start Tor Browser 7.0, the process appears on the task manager, but that disappears in a moment. So I am using Tor Browser 6.5.

AAA (not verified) said:

June 14, 2017

Permalink

Thank you for replying. I am using Windows 10 (64 bit version). Tor Browser 6.5 starts normally, but 7.0 and 7.0.1 and 7.5a1 won't start.

AAA (not verified) said:

June 17, 2017

Permalink

I stopped my ESET Smart Security, but TorBrowser.exe still disappears from the task manager.

AAA (not verified) said:

June 14, 2017

Permalink

Also, my Tor Browser 6.5 asked me to upgrade to 6.51.

6.51 started normally, but 7.0 or later never start.

Nathan barly (not verified) said:

June 15, 2017

Permalink

Any for Tor Browser to change back "Highlight All" keyboard shortcut to "Alt+A", instead of Mozilla's change to "Alt+L".

The change now affect TBB, after the move to Firefox 52 ESR.
Mozilla apparently made the change to accommodate Mac users, but made change to all distributions.
"Alt+L" is very annoying, for it is no longer a simple one-handed operation as "Alt+A".

The change can be found here:
https://bugzilla.mozilla.org/show_bug.cgi?id=435326

The resources that have the change are apparently:
* view-source:resource://gre/chrome/en-US/locale/en-US/global/findbar.dtd
* view-source:chrome://global/locale/findbar.dtd

If this is the best place to post this, could someone please refer me where to go, thanks.

Torguy (not verified) said:

June 15, 2017

Permalink

" Since the update, Tor does not save my adjustment to the network setting and about:config, meaning I have to re-do at each browser launch. Anyone have any idea what happened?

Submitted by toruser39284 (not verified) on June 08, 2017

" Could you give us steps how to reproduce your problem? What exactly did you do which worked in the past but does not do so now anymore? "
Submitted by gk on June 09, 2017

In reply to Since the update, Tor does… by toruser39284

" I’m just using the Tor browser without the Tor network by going into network settings and selecting “No Proxy”. Then in “about:config” going to “network.proxy.socks_remote_dns” and Toggling. These settings do not save after I quit the browser and must re-do each time I launch the browser. Previous versions saved these configuration changes and would not require me to do this every time on browser launch.

I have been awaiting an answer on this. Latest update did not address this problem. Please let me know.

Anon (not verified) said:

June 16, 2017

Permalink

Sorry to bother you guys, but Tor browser 7.x doesn't work for me, no matter what OS I use.

To cut it short, I have Tor browser 6.5.2 running fine on my windows 7 desktop computer, a few day ago it automatically downloaded 7.0 update, the next time I try to run it, the progress bar stuck at 'retrieving network status' stage, waiting overnight and nothing happens.

Suspecting a corrupted update, I deleted that installation, rolled back to a clean 6.5.2 browser, and downloaded a fresh 7.0 installation file, loaded the same set of obfs4 bridges to the newly installed Tor browser7.0, and it didn't help, when I run it, the progress bar still stuck at 'retrieving network status'.

Alarmed, I checked the log file, and witnessing a crapload of ''Ignoring directory request, since no bridge nodes are available yet." warning, also the exact place where the bootstrap process is '25% asking for network consensus'.

Since I also have a flashdisk loaded with tails 2.12, I decided to do a signature verification, both 6.5.2 binary file and 7.0 turned out ok.

To rule out any antivirus false-positive or network hardware/driver based failures, I booted from tails 2.12, and downloaded a fresh image of tails 3.0 through Tor browser, and burned it to a DVD disk, when I booted from the tails 3.0 DVD, and try to connect to tor network, again using the same set of obfs4 bridges, the same symptom happens, the progress bar won't go past 'retrieving network status' stage. A quick look through the log created again revealing a series of 'Ignoring directory request, since no bridge nodes are available yet.' warning, occasionally, 'I learned some more directory information, but not enough to build a circuit: We have no usable consensus. ' appears. Waiting for hours doesn't make any differences.

From those symptoms, I can only draw the conclusion that either this particular version of Tor browser has some pluggable transport related coding issue, or the country I live in has come up with some particular effective measure to attack the bootstrapping process of tor browser 7.0.

I'm at a total loss here, can anyone share their experience with TBB7.0 or tails 3.0?

BTW my ISP is China telecom.

Andy (not verified) said:

June 17, 2017

Permalink

I have had Tor on two of my Macs (OS X10.6.8 & 10.8.5) for only a few months, and have generally enjoyed using it without really understanding it. I do, however understand and completely agree with the need for anonymous browsing for ordinary citizens.
This morning the browser on the 10.8.5 mac wouldn't boot-- giving me the following error msg in a Finder Window: "...you have OSX 10.8.5. the Application requires OSX 10.9 or later."
I do not recall installing or approving an install of an updated version or Tor in the last several days.
I tried rebooting & re-loading the Tor Browser but got the same results. I cannot use Tor on my 10.8.5 machine, nor can I find any workarounds on your site. (I am writing this from my 10.6.8 machine, by the way.)

Now I have two Qs:
1- How can I retrieve the earlier version of Tor Browser to restore the Tor connection to my 10.8.5 machine?
2- How can I prevent this from happening to my to.6.8 machine?

Note:
I must honestly admit that I am computer-challenged, and don't understand much of computer-speak. I am not qualified to mess with my Terminal nor have I even seen this thing called the Registry on any of my computers.
Layman-speak, insofar as it is possible, will be appreciated.
Thanks. Andy 6/17/17

Generally speaking: Tor Browser now requires OS X 10.9 as the minimum on Apple computers. That is a new requirement that came with the switch to Firefox 52. That you got it on your 10.8.5 system is probably due to a bug we recently fixed (https://trac.torproject.org/projects/tor/ticket/22558), it should not happen again. Now, if you just use your 10.6.8 machine you won't get Tor Browser 7 with all the important security updates. You will stay on the unsecure 6.5.2. The same will happen on your 10.8.5 machine once you have an older Tor Browser version there as well. All the released versions can be found on https://archive.torproject.org/tor-package-archive./torbrowser/.

Jake (not verified) said:

July 03, 2017

Permalink

This new version of TBB is going to take some getting used to. I'm no computer guru by any stretch of the imagination and have no technical skill in computer sciences/IT etc but I do love exploring around in the deep. It's really quite fascinating what kind of stuff is in those depths - many times very interesting and of course at other times rather morbid to say the least. I love the feeling I get when I'm just about to open an onion link (however risky it may be and I am aware of that - I do so at my own risk ) that I've not seen, don't recognize and have no indication of what it might be and no idea of what I'm about to enter into. That little rush that comes over me like sitting in a horror movie waiting for the main character to do this or that and it's all suspenseful and I'm all on the edge of my seat. I love it, can't beat it.

I'm curious to know where the visual feedback offered up by the last version of TBB disappeared to??? For example, in the most recent version of TBB, at the top left of the browser's URL I could change my session, I could change my identity or (sad but true, most intriguing part to me) I could pull down a drop list where I could see the various hops that my data would travel across.

Would someone, anyone be so kind as to direct me to where I can either see this information or explain which add-ons or modifications I might need to make so that I can enable this information once more - or perhaps it's just under my nose and I'm overlooking it entirely. Yes, I know never to modify the browser for security reasons (and I never have). I just can't imagine this would be OK to do now but I'll sure look forward to having that information again.

Thanks in advance@

Anonymous (not verified) said:

July 08, 2017

Permalink

An important change that you should have pointed out in the release announcement for 7.0.

If TBB refuses to start, and exits with errors like Could not bind to 127.0.0.1:9150: Address already in use, you should check your torrc configuration file and remove any lines starting with SocksPort or ControlPort left over from older TBB releases.

At least, this fixed the problem for me. Corrections and more details are appreciated.

That depends. Are you running Windows on it? Then it should not. However it is not clear what happens in this case. Could you give it a try and report back what is happening in that case?

Assuming it is not working for you, could you do us an additional favor and test a build that is supposed to warn users when installing Tor Browser on Windows on a non-SSE2 machine? We did not find such a machine yet and could therefore not verify whether our patch behaves correctly. The bundle can be found on:

https://people.torproject.org/~boklm/bug_21704/torbrowser-install-7.0a4…
https://people.torproject.org/~boklm/bug_21704/torbrowser-install-7.0a4…

Thanks!

Devin (not verified) said:

March 08, 2018

Permalink

How about you people quit making this security shit so god damn hard to install. Seriously, I just downloaded the Linux Tor browser "sandbox". But it's not really a sandbox because it keeps asking for some fucking binary file that is not with it. I thought you people were suppose to be smart? Make it where you can just download all the fucking shit that's required in one package. Stop making life complicated.