New Release: Tor Browser 9.0

Update [7:30 UTC]: Clarified the amount of locales we support. It's 32 with Tor Browser 9.0.

Update [10:45 UTC]: Added a section about letterboxing.

Tor Browser 9.0 is now available from the Tor Browser download page and also from our distribution directory.

This release features important security updates to Firefox.

Tor Browser 9.0 is the first stable release based on Firefox 68 ESR and contains a number of updates to other components as well (including Tor to and OpenSSL to 1.1.1d for desktop versions and Tor to for Android).

In addition to all the needed patch rebasing and toolchain updates, we made big improvements to make Tor Browser work better for you.

We want everyone in the world to be able to enjoy the privacy and freedom online Tor provides, and that's why over the past couple years, we've been working hard to boost our UX and localization efforts, with the biggest gains first visible in Tor Browser 8.0.

In Tor Browser 9.0, we continue to build upon those efforts with sleeker integration and additional localization support.

Goodbye, Onion Button

We want your experience using Tor to be fully integrated within the browser so how you use Tor is more intuitive. That's why now, rather than using the onion button that was in the toolbar, you can see your path through the Tor network and request a New Circuit through the Tor network in [i] on the URL bar.

Tor Browser - circuit display - dark theme


Hello, New Identity Button

Tor Browser - Toolbar - New Identity Button

Instead of going into the onion button to request a New Identity, we've made this important feature easier to access by giving it its own button in the toolbar.

Tor Browser - New Identity

You can also request a New Identity, and a New Circuit, from within the [=] menu on the toolbar.

Torbutton and Tor Launcher Integration

Now that both extensions are tightly integrated into Tor Browser, they'll no longer be found on the about:addons page.

Tor Browser - about preferences

We redesigned the bridge and proxy configuration dialogs and include them directly into the browser's preference settings as well.

Rather than being a submenu behind the onion button, Tor Network Settings, including the ability to fetch bridges to bypass censorship where Tor is blocked, are easier to access on about:preferences#tor.


Tor Browser, in its default mode, is starting with a content window rounded to a multiple of 200px x 100px to prevent fingerprinting the screen dimensions. The strategy here is to put all users in a couple of buckets to make it harder to single them out. That worked until users started to resize their windows (e.g. by maximizing them or going into fullscreen mode). Tor Browser 9 ships with a fingerprinting defense for those scenarios as well, which is called Letterboxing, a technique developed by Mozilla and presented earlier this year. It works by adding white margins to a browser window so that the window is as close as possible to the desired size while users are still in a couple of screen size buckets that prevent singling them out with the help of screen dimensions.

Better Localization Support

If we want all people around the world to be able to use our software, then we need to make sure it's speaking their language. Since 8.0, Tor Browser has been available in 25 languages, and we added 5 locales more in Tor Browser 8.5. Today, we add support for two additional languages: Macedonian (mk) and Romanian (ro), bringing the number of supported languages to 32.

We also fixed bugs in our previously shipped localized bundles (such as ar and ko).

Many thanks to everyone who helped with these, in particular to our translators.

Known Issue

As usual when preparing Tor Browser releases, we verified that the build is bit-for-bit reproducible. While we managed to get two matching builds, we found that in some occasions the builds differ (we found this happening on the Linux i686 and macOS bundles). We are still investigating the cause of this issue to fix it.

Give Feedback

If you find a bug or have a suggestion for how we could improve this release, please let us know. Thanks to all of the teams across Tor, and the many volunteers, who contributed to this release.


The full changelog since Tor Browser 8.5.6 is:

  • All Platforms
    • Update Firefox to 68.2.0esr
    • Bug 31740: Remove some unnecessary RemoteSettings instances
    • Bug 13543: Spoof smooth and powerEfficient for Media Capabilities
    • Bug 28196: about:preferences is not properly translated anymore
    • Bug 19417: Disable asmjs on safer and safest security levels
    • Bug 30463: Explicitly disable MOZ_TELEMETRY_REPORTING
    • Bug 31935: Disable profile downgrade protection
    • Bug 16285: Disable DRM/EME on Android and drop Adobe CDM
    • Bug 31602: Remove Pocket indicators in UI and disable it
    • Bug 31914: Fix eslint linter error
    • Bug 30429: Rebase patches for Firefox 68 ESR
    • Bug 31144: Review network code changes for Firefox 68 ESR
    • Bug 10760: Integrate Torbutton into Tor Browser directly
    • Bug 25856: Remove XUL overlays from Torbutton
    • Bug 31322: Fix about:tor assertion failure debug builds
    • Bug 29430: Add support for meek_lite bridges to bridgeParser
    • Bug 28561: Migrate "About Tor Browser" dialog to tor-browser
    • Bug 30683: Prevent detection of locale via some *.properties
    • Bug 31298: Backport patch for #24056
    • Bug 9336: Odd wyswig schemes without isolation for
    • Bug 27601: Browser notifications are not working anymore
    • Bug 30845: Make sure internal extensions are enabled
    • Bug 28896: Enable extensions in private browsing by default
    • Bug 31563: Reload search extensions if extensions.enabledScopes has changed
    • Bug 31396: Fix communication with NoScript for security settings
    • Bug 31142: Fix crash of tab and messing with about:newtab
    • Bug 29049: Backport JS Poison Patch
    • Bug 25214: Canvas data extraction on local pdf file should be allowed
    • Bug 30657: Locale is leaked via title of link tag on non-html page
    • Bug 31015: Disabling SVG hides UI icons in extensions
    • Bug 30681: Set security.enterprise_roots.enabled to false
    • Bug 30538: Unable to comment on The Independent Newspaper
    • Bug 31209: View PDF in Tor Browser is fuzzy
    • Translations update
  • Windows + OS X + Linux
    • Update Tor to
    • Update OpenSSL to 1.1.1d
      • Bug 31844: OpenSSL 1.1.1d fails to compile for some platforms/architectures
    • Update Tor Launcher to
      • Bug 28044: Integrate Tor Launcher into tor-browser
      • Bug 32154: Custom bridge field only allows one line of input
      • Bug 31286: New strings for about:preferences#tor
      • Bug 31303: Do not launch tor in browser toolbox
      • Bug 32112: Fix bad & escaping in translations
      • Bug 31491: Clean up the old meek http helper browser profiles
      • Bug 29197: Remove use of overlays
      • Bug 31300: Modify Tor Launcher so it is compatible with ESR68
      • Bug 31487: Modify moat client code so it is compatible with ESR68
      • Bug 31488: Moat: support a comma-separated list of transports
      • Bug 30468: Add mk locale
      • Bug 30469: Add ro locale
      • Bug 30319: Remove FTE bits
      • Translations update
    • Bug 32092: Fix Tor Browser Support link in preferences
    • Bug 32111: Fixed issue parsing user-provided bridge strings
    • Bug 31749: Fix security level panel spawning events
    • Bug 31920: Fix Security Level panel when its toolbar button moves to overflow
    • Bug 31748+31961: Fix 'Learn More' links in Security Level preferences and panel
    • Bug 28044: Integrate Tor Launcher into tor-browser
    • Bug 31059: Enable Letterboxing
    • Bug 30468: Add mk locale
    • Bug 30469: Add ro locale
    • Bug 29430: Use obfs4proxy's meek_lite with utls instead of meek
    • Bug 31251: Security Level button UI polish
    • Bug 31344: Register SecurityLevelPreference's 'unload' callback
    • Bug 31286: Provide network settings on about:preferences#tor
    • Bug 31886: Fix ko bundle bustage
    • Bug 31768: Update onboarding for Tor Browser 9
    • Bug 27511: Add new identity button to toolbar
    • Bug 31778: Support dark-theme for the Circuit Display UI
    • Bug 31910: Replace meek_lite with meek in circuit display
    • Bug 30504: Deal with New Identity related browser console errors
    • Bug 31929: Don't escape DTD entity in ar
    • Bug 31747: Some onboarding UI is always shown in English
    • Bug 32041: Replace = with real hamburguer icon ≡
    • Bug 30304: Browser locale can be obtained via DTD strings
    • Bug 31065: Set network.proxy.allow_hijacking_localhost to true
    • Bug 24653: Merge into torbutton.dtd
    • Bug 31164: Set up default bridge at Karlstad University
    • Bug 15563: Disable ServiceWorkers on all platforms
    • Bug 31598: Disable warning on window resize if letterboxing is enabled
    • Bug 31562: Fix circuit display for error pages
    • Bug 31575: Firefox is phoning home during start-up
    • Bug 31491: Clean up the old meek http helper browser profiles
    • Bug 26345: Hide tracking protection UI
    • Bug 31601: Disable recommended extensions again
    • Bug 30662: Don't show Firefox Home when opening new tabs
    • Bug 31457: Disable per-installation profiles
    • Bug 28822: Re-implement desktop onboarding for ESR 68
  • Windows
    • Bug 31942: Re-enable signature check for language packs
    • Bug 29013: Enable stack protection for Firefox on Windows
    • Bug 30800: ftp:// on Windows can be used to leak the system time zone
    • Bug 31547: Back out patch for Mozilla's bug 1574980
    • Bug 31141: Fix typo in font.system.whitelist
    • Bug 30319: Remove FTE bits
  • OS X
    • Bug 30126: Make Tor Browser compatible with macOS 10.15
    • Bug 31607: App menu items stop working on macOS
    • Bug 31955: On macOS avoid throwing inside nonBrowserWindowStartup()
    • Bug 29818: Adapt #13379 patch for 68esr
    • Bug 31464: Meek and moat are broken on macOS 10.9 with Go 1.12
  • Linux
    • Bug 31942: Re-enable signature check for language packs
    • Bug 31646: Update abicheck to require newer
    • Bug 31968: Don't fail if /proc/cpuinfo is not readable
    • Bug 24755: Stop using a heredoc in start-tor-browser
    • Bug 31550: Put curly quotes inside single quotes
    • Bug 31394: Replace "-1" with "−1" in start-tor-browser.desktop
    • Bug 30319: Remove FTE bits
  • Android
    • Update Tor to
    • Bug 31010: Rebase mobile patches for Fennec 68
    • Bug 31010: Don't use addTrustedTab() on mobile
    • Bug 30607: Support Tor Browser running on Android Q
    • Bug 31192: Support x86_64 target on Android
    • Bug 30380: Cancel dormant by startup
    • Bug 30943: Show version number on mobile
    • Bug 31720: Enable website suggestions in address bar
    • Bug 31822: Security slider is not really visible on Android anymore
    • Bug 24920: Only create Private tabs in permanent Private Browsing Mode
    • Bug 31730: Revert aarch64-workaround against JIT-related crashes
    • Bug 32097: Fix conflicts in mobile onboarding while rebasing to 68.2.0esr
  • Build System
    • All Platforms
      • Bug 30585: Provide standalone clang 8 project across all platforms
      • Bug 30376: Use Rust 1.34 for Tor Browser 9
      • Bug 30490: Add cbindgen project for building Firefox 68 ESR/Fennec 68
      • Bug 30701: Add nodejs project for building Firefox 68 ESR/Fennec 68
        • Bug 31621: Fix node bug that makes large writes to stdout fail
      • Bug 30734: Add nasm project for building Firefox 68 ESR/Fennec 68
      • Bug 31293: Make sure the lo interface inside the containers is up
      • Bug 27493: Clean up mozconfig options
      • Bug 31308: Sync mozconfig files used in tor-browser over to tor-browser-build for esr68
    • Windows
      • Bug 29307: Use Stretch for cross-compiling for Windows
      • Bug 29731: Remove faketime for Windows builds
      • Bug 30322: Windows toolchain update for Firefox 68 ESR
        • Bug 28716: Create mingw-w64-clang toolchain
        • Bug 28238: Adapt firefox and fxc2 projects for Windows builds
        • Bug 28716: Optionally omit timestamp in PE header
        • Bug 31567: NS_tsnprintf() does not handle %s correctly on Windows
        • Bug 31458: Revert patch for #27503 and bump mingw-w64 revision used
      • Bug 9898: Provide clean fix for strcmpi issue in NSPR
      • Bug 29013: Enable stack protection support for Firefox on Windows
      • Bug 30384: Use 64bit containers to build 32bit Windows Tor Browser
      • Bug 31538: Windows bundles based on ESR 68 are not built reproducibly
      • Bug 31584: Clean up mingw-w64 project
      • Bug 31596: Bump mingw-w64 version to pick up fix for #31567
      • Bug 29187: Bump NSIS version to 3.04
      • Bug 31732: Windows nightly builds are busted due to mingw-w64 commit bump
      • Bug 29319: Remove FTE support for Windows
    • OS X
      • Bug 30323: MacOS toolchain update for Firefox 68 ESR
      • Bug 31467: Switch to clang for cctools project
      • Bug 31465: Adapt tor-browser-build projects for macOS notarization
    • Linux
      • Bug 31448: gold and lld break linking 32bit Linux bundles
      • Bug 31618: Linux32 builds of Tor Browser 9.0a6 are not matching
      • Bug 31450: Still use GCC for our ASan builds
      • Bug 30321: Linux toolchain update for Firefox ESR 68
        • Bug 30736: Install yasm from wheezy-backports
        • Bug 31447: Don't install Python just for Mach
      • Bug 30448: Strip Browser/gtk2/
    • Android
      • Bug 30324: Android toolchain update for Fennec 68
        • Bug 31173: Update android-toolchain project to match Firefox
        • Bug 31389: Update Android Firefox to build with Clang
        • Bug 31388: Update Rust project for Android
        • Bug 30665: Get Firefox 68 ESR working with latest android toolchain
        • Bug 30460: Update TOPL project to use Firefox 68 toolchain
        • Bug 30461: Update tor-android-service project to use Firefox 68 toolchain
      • Bug 28753: Use Gradle with --offline when building the browser part
      • Bug 31564: Make Android bundles based on ESR 68 reproducible
      • Bug 31981: Remove require-api.patch
      • Bug 31979: TOPL: Sort dependency list
      • Bug 30665: Remove unnecessary build patches for Firefox

October 23, 2019


Have been testing Tor Browser 9.0 in Tails 4.0 and it seems to be working very well!

Also tested things like burning DVDs in Tails 4.0 and all seems well.

Very noticeable improvements in Spectre/Meltdown mitigations which were causing some problems in older Tails.

Many thanks to Tails Project and to Tor Project for all your hard work!


October 23, 2019


Many thanks for the letterboxing feature which addresses a concern I and others expressed in this blog!


October 23, 2019


Is there a way of turning off the letterboxing ? It's really annoying and unaesthetic It just looks awful. While I appreciate the effort, I'm not overly worried about fingerprinting for most sites I visit, and basic UI stuff also matters.

Also I had to customize in the toolbar to remove the new 'sweep' button that's replaced the onion for New Identity. It just deletes your session without warning and that's also very bad. I often have multiple tabs open with Tor Browser when I'm doing research and that's just a really bad idea to have a button that can instantly wipe your session.

You are getting the warning on the first time and if you decide to not get warned anymore you won't. Otherwise you get every time you click on the New Identity button the warning whether you really want to do a New Identity now or not. I think we should not make it even harder to just get back to a clean session slate.

Sure, you can disable it Letterboxing by flipping privacy.resistFingerprinting.letterboxing to false.

I'm not overly worried about fingerprinting for most sites I visit

That's great for you, but what happens when you are worried? And what happens to everyone else? If a large group of users turns off letterboxing, that degrades its goal to help everyone blend in. Anonymity loves company. To quote gk: Do you have some ideas on how to make letterboxing better so you would not disable it?

the new 'sweep' button... deletes your session without warning

No, it doesn't unless you, yourself, clicked on "Never ask me again". To reactivate the confirmation prompt, open a new tab, type about:config, search for extensions.torbutton.confirm_newnym, and toggle or reset it back to true, the default.

> I often have multiple tabs open with Tor Browser when I'm doing research and that's just a really bad idea to have a button that can instantly wipe your session.

FWIW, I do a great deal of online research using TB under Tails, and I use "new identity" a lot but avoid tabs. That works for me but one does need to be more disciplined about the order of operations.

I consider the fact that the location pane doubles as a search pane to be quite tricky. I've gotten better at using this effectively, but IMO this feature should have been carefully explained in the announcement when it was new to TB but this did not happen.

The problem with "gestures" and mysterious never-before-seen icons is that users need to be clearly told how to use them properly, and ironically it can take more words to explain a gesture than it would take to explain a purely text based command.

If users are expected to guess what new features do and why, they could potentially do something dangerous. So IMO learning by trial and error is not a good idea for security-critical software.

I think this is one of the biggest long-standing issues with the "new version of Tor Browser" announcements: blog posters aren't thinking carefully enough about what ordinary users (e.g. people unfamiliar with the latest FF or the latest smart phone) can reasonably be expected to know.

In another comment, someone else suggested (I think) that a bug in Tor Browser might explain problems I have noticed trying to use the Debian onions when I update my Debian 10 system on a desktop PC:

Has that been fixed in Tor Browser 9.0?

I'd like to ask Tor Project to work with Debian Project to ensure that the Debian onions are protected by health checks, and if they are overloaded, to work to add capacity.

Further, I'd like to ask Tor Project to reach out to R Project to try to mirror CRAN on an onion, with suitable checks that the mirror is kept secure/accurate.

Would it be utterly impractical to use Tor with a Raspberry Pi? If not, can you post a guide? And can you work with Raspbian to mirror their repo on an onion?

Thanks for all your hard work!

I don't have an answer for your Debian 10 system, but...

> I'd like to ask Tor Project to work with Debian Project to ensure that the Debian onions.... Further, reach out to R Project... work with Raspbian...

You seek Peter Palfrader. He manages the onions for both Tor Project and Debian (name in footers at bottom) and the tor package for Debian. As for R Project and Raspbian, while you're asking Tor Project to reach out, ask those other projects to reach out to TP at the same time, too. Coordinate introducing them.

> Tor with a Raspberry Pi?

There are similar comments in this blog post and ticket #12631 for ARM architecture:

According to those, it sounds difficult at the current stage of development and thus impractical for general users but not impossible. See the ticket for guides.

Just wanted to say that the new identity button seems to be working great in Tor Browser 9.0 under Tails 4.0.

I complained in a previous post about removing the onion icon but I now see I misunderstood so I withdraw my complaint about that :-)

Thanks for all your hard work!

Secure Connection Failed
An error occurred during a connection to PR_END_OF_FILE_ERROR

Regarding the problems reported in some comments about using Tor Browser 9.0 with Linux and seeing that their OS is reported as Linux not Windows:

For what it is worth, I just tested this using Tor Browser 9.0 in Tails 4.0 (based on Debian 10) and got the expected result:

> HTTP_USER_AGENT Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Firefox/68.0

I'm running macOS "Mojave" version 10.14.6 on a four-year-old iMac. Yesterday, 2019.10.22, Tor Browser offered to upgrade my version of Tor from 8.5.5 to 9.0. I allowed the upgrade to proceed. This morning when I logged back into my iMac I discovered I cannot use Tor to log into my ProtonMail account, nor can I see Apple's System Status web page (, as I routinely can. But if I use Firefox, I can see Apple's System Status web page and I can log into my ProtonMail account. That suggests to me that Tor 9.0 is broken in that respect. Also, I can use Tor to get to other web sites, such as this one where I'm providing this information to you. Those web sites display load promptly and display fine — just not Apple's System Status page and ProtonMail. Whoops. Just found another web page that won't display: Your "get in touch with us" ( web page mentioned right here on this web page I am using to reply to you. Clicking that link returns "404 Not Found" in Tor 9.0.

Do you know where you found the "get in touch with us" web page?

That said I am not sure about the other two. What errors do you get for them?

> Do you know where you found the "get in touch with us" web page?

It's on the blog pages, at the bottom where it says "Join the discussion"

404 is a response from a site's web server that indicates a missing page on the web server. If you see a green padlock on a 404 page, then Tor is most likely running properly, and the site's web server is the thing that's having problems. 404 should not be confused with a browser's internal error messages indicating network or DNS problems such as "We’re having trouble finding that site," "Check your network connection".

If the server does not respond at all, not even with an HTTP error message, write down the date and time with timezone, the URL, and the IPs of your circuit from the circled [i] in the address bar on that tab. See if other sites open in that session. Try clicking the New Identity button and opening Apple's and ProtonMail's "broken" pages again. Both open fine for me. Still broken? Search for one of those uptime status or "Is it down?" websites, and see if it really is down for everyone. Was it just you? Relays go offline sometimes. If you think it was suspicious, consider reporting the relays:

How did you find that torproject link? I found a page on the Support site with an identical title: How to Report a Bug or Give Feedback but didn't find what links to your link.

We look into it in This seems to be some Cloudflare bullshit.

I have the same bug sometimes. Seems to be caused by "Accept" header, which now is "image/webp,*/*" instead of "*/*" in the previous versions (this changed in Firefox with introducting the webp images support). Some servers somehow don't like that and return 403 error instead of a image.

Good looking new New Identity broom sweep icon. It looks dissimilar to the other icons and illustrates its meaning reasonably well. Although it looks closer to meaning "clean up", the word "identity" is hard to visualize except for yet another rectangular shaped icon for an ID card or a silhouette of a head and shoulders for "persona" but lacking an action.

But you made the Bridges and Proxy preferences harder to find. Gotta update the FAQ and the manual.

> Good looking new New Identity broom sweep icon. It looks dissimilar to the other icons and illustrates its meaning reasonably well.

Plus one.

What's with the horrible light border? I use a dark theme and the new border is just daft. Please put it back to the way it was. Cheers.

It's just a reminder that you're doing something wrong with the size of your window ;)

We plan to fix that light border in Stay tuned.

I am using Tor Browser 9.0 in Tails 4.0. Just wanted to say that using the pane to send a search query to the DuckDuckGo onion seems to be working fine and is noticeably faster than with previous versions :-)

Many thanks for all your hard work!

Letterboxing, a technique developed by Mozilla

Not based on or co-developed? Your ZDNet source repeatedly cites Tor Project as the original developer of the technique that inspired Mozilla whose modification made its way back into Tor Browser. (Hooray for libre software licenses!) Arthur Edelstein of Tor Project was even the reporter of Mozilla's Bugzilla ticket.

I think Mozilla got inspired by it but they did essentially all the hard work (in particular Tom Ritter did so, thanks Tom for all your work here).

bringing the number of supported languages to 32

Translators, please bring that many to the website, support, manual.

Unfortunately comments are closed in

but Tails 4.0 includes OnionShare 1.3.2. This is better than the previous version, but it is not yet OnionShare 2.2, which has possibly desirable features as explained in…

On the face of it, "amnesia" might not seem fully compatible with publishing an anonymous website using OnionShare, but I hope Tails Project will consider upgrading to OnionShare 2.2 in the next edition of Tails, if that is possible and if it does not introduce security issues.

Until about a year ago, Tails Project was apparently working on a "Tails server" which would, I guess, have offered something similar to what the combination of Tails 4.1 and OnionShare 2.2 would appear to offer, if OnionShare 2.2 is included in Tails 4.1 (which would be I presume the next edition after Tails 4.0, the current edition).

I am using Tor Browser 9.0 in Tails 4.0 and so far it's great!

Wanted to shout out to Tails Project for fixing (apparently) a problem with Whisperback error reporting, which is now working again for me.

Also, I have a laptop whose hard drive is failing, so I now use it only by booting Tails from a DVD. When I do this with Tails 4.0, I get a popup warning me that the disk is failing. This is actually a very good thing because if I did not already know that, I would want to know it!

Many thanks to Tor Project and Tails Project for all your hard work!

Search the Tails menu for disk utilities. See if they have a feature to read a hard drive's S.M.A.R.T. data. If you can't find one, see if GSmartControl is installed. If not, you can install it from your software package manager or by opening a terminal and typing: sudo apt-get install gsmartcontrol Be careful not to do anything that could further harm the disk. Personally, I would open the case and unplug the disk until I had a reliable disk (or USB drive, another computer, trusted cloud storage, or DVD-Rs) to backup its data. A good internal hard drive is not expensive to replace relative to other components: about $40 USD, but you may need one of the things in parentheses or a USB enclosure to transfer data between them if you don't have a spare storage device or can't plug in both drives at the same time. Good luck.

> Search the Tails menu for disk utilities. See if they have a feature to read a hard drive's S.M.A.R.T. data.

Yes, it does, and I presume that this exactly where the popup message comes from.

Fortunately I had nothing of value on that hard drive. I see value in keeping it to befuddle the bad guys if someone steals the laptop.

I am using Tor Browser 9.0 in Tails 4.0. Just wanted to shout out to Tails Project (again!) for another indication of the care they took in making Tails 4.0: when you boot Tails in on-line mode, connect to Tor network, and press the "Tails Documentation" icon on the desktop, you call up Tor Browser and see the documentation at the Tails website. But when you boot Tailos in off-line mode and press that icon, you see the version in file:///usr/share/doc/tails/website/ which is what should happen. Nice!

Using TB9 without tor seems to be impossible. I set use_nontor_proxy = true, proxy.type = 0, but pages won't load. Is it a bug or TB just dropped support for nontor setups? Please, say it's a bug.

We don't have dropped support. Maybe is your bug (although I am not convinced yet that it is actually one).

The preferences are still there, it doesn't work as expected though:
extensions.torlauncher.start_tor false
network.proxy.socks_remote_dns false
network.proxy.type 0
use_nontor_proxy = true
proxy.type = 0

works fine - until restart. Restarting Tor Browser will inevitably reset 2+3 in about:config for some reason.

You might wan to note that on the ticket, thanks! It would be helpful to track down the parts that lead to this change, too. Feel free to do so as we won't have time for that.

Small bug with the Russian version: The country names in the circuit overview are not localized anymore, they now show up in English. Used to be translated.

as always great work!
i like the new button for new session, makes it much easier and faster zu do it.

i still have a problem with google captachs. i do them, but it still says it's wrong. help please!

> google captachs. i do them, but it still says it's wrong.

When I find sites like those, I just don't use those sites. No access = no patronage or clicks from me. Find and promote competitors of theirs who accept (and better yet, support) Tor. Here are some ISPs and hosting companies, too.

Website administrators should also learn that many other captcha methods exist that do not break their site through Tor.

Something broke up since Tor Browser 8.5. In 8.5, I launch "D:\Tor Browser\Browser\firefox.exe" -osint and have ability to open links in new tabs of tor browser by clicking to them from other app (thunderbird).
Now with 9.0 release it looks like "-osint" option disappeared - tor browser doesn't even start from shortcut when it has this option specified!

here are the strings I have in registry:

[HKEY_CURRENT_USER\SOFTWARE\Tor Browser\Capabilities]
"ApplicationDescription"="Tor Browser"
"ApplicationIcon"="D:\\Tor Browser\\Browser\\firefox.exe,0"
"ApplicationName"="Tor Browser"

[HKEY_CURRENT_USER\SOFTWARE\Tor Browser\Capabilities\FileAssociations]

[HKEY_CURRENT_USER\SOFTWARE\Tor Browser\Capabilities\URLAssociations]

; Register to Default Programs

"Tor Browser"="Software\\Tor Browser\\Capabilities"

; TorBrowserURL HANDLER:

@="Tor Browser Document"
"FriendlyTypeName"="Tor Browser Document"



@="\"D:\\Tor Browser\\Browser\\firefox.exe\" -osint -url \"%1\""

and, with Tor Browser 8.5 opening of links in new tabs of TB from other application worked OK. But now in 9.0 - it doesn't. It doesn't even start with -osint parameter!

Does that work in a recent Firefox because Mozilla released fixes for security problems around it a bit back that might be the reason for your trouble.

osint is a Mozilla Firefox command line option. Tor Browser 8.5.5 was based on Firefox 60.9.0 ESR. Tor Browser 9.0 is based on Firefox 68.2.0 ESR. Browse Firefox's release notes to find what changed. I did a quick search and couldn't find osint.

Mozilla Support Forum:
can't open links from office 2016 or thunderbird
Why won't Links open from e-mail if Firefox is default browser

Guys, add site translation, like on chrome, this will be great!

Join the discussion...

We encourage respectful, on-topic comments. Comments that violate our Code of Conduct will be deleted. Off-topic comments may be deleted at the discretion of the post moderator. Please do not comment as a way to receive support or report bugs on a post unrelated to a release. If you are looking for support, please see our support portal or ways to get in touch with us.

This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.

13 + 7 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.