New Release: Tor Browser 9.5.3

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

This release updates Firefox to 68.11.0esr, NoScript to 11.0.34, and Tor to 0.4.3.6.

Also, this release features important security updates to Firefox.

The full changelog since Tor Browser 9.5.1 is:

  • All Platforms
    • Update Firefox to 68.11.0esr
    • Update NoScript to 11.0.34
    • Update Tor to 0.4.3.6
Anonymous

August 04, 2020

Permalink

y is the same thing copy pasted in full changelogs ?
isnt it meant to be detailed ?
like what changes actually came with these ?

Update NoScript to 11.0.34
Update Tor to 0.4.3.6

Anonymous

August 05, 2020

Permalink

"The bookmarks and history system will not be functional because one of Firefox's files is in use by another application. Some security software can cause this problem."

Downloaded earlier versions, installed them and this problem vanishes!

Anonymous

August 06, 2020

Permalink

I am also getting the same message about bookmarks and history system not being functional and when I try to download something...nothing happens...check the library and it is blank. Here is the specific message. I tried all the suggested solutions and none worked:

The bookmarks and history system will not be functional because one of the Tor Browser's files is in use by another application. Some security software can cause this problem.

Anonymous

August 06, 2020

Permalink

What is problem??help me.

"Couldn't sign you in This browser or app may not be secure. Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in."

Anonymous

August 07, 2020

Permalink

What are the benefits of constant private mode over regular customized mode with no history and delete everything on close?

Anonymous

August 08, 2020

Permalink

Hi . I cannot disable ipv6 . And snowflakes is not appareing. Bridge :Obfs 4 or Azure . The only one solution to block ipv6 is behind a vpn . Or using new Orbot version and let them working both.

Anonymous

August 09, 2020

Permalink

Is there a reason TOR options are not available in preferences on a Tails 9.5.3 install?

Anonymous

August 11, 2020

Permalink

This description of a defect in 9.5.3 is being presented in this forum because the read-only Tor Trac Bug Tracker and Wiki site did not migrate my account to The Tor Project's Gitlab! site, and The Tor Project's Gitlab! site has not replied to my request for Account Creation.

Testing proves this defect is equally present in versions 9.5.3, 9.5.1, and 9.5, but it is not present in 9.0.10, 9.0.9, and 9.0.4.

In 9.5.3 (and in the aforementioned versions) setting modified configuration about:config > layout.css.devPixelsPerPx Value 2.4 is necessary to prevent user eyestrain and eye fatigue when using Tor Browser on MacBook Air 13-inch laptop.

However, when 9.5.3 (and 9.5.1 and 9.5) is using modified Value 2.4 when the browser starts, the window opens at screen resolution w:998 x h:599 across browser sessions, letterboxing displays the screen resolution at w:348 x h:399 and w:798 x h:599 across sessions when adjusting the window size manually, and Enter Full Screen displays the screen resolution at w:1198 x h:599 across sessions.

In 9.5.3 (and in 9.5.1, 9.5, 9.0.10, 9.0.9, and 9.0.4) selecting modified Value 3.0 and restarting Tor Browser opens the window at screen resolution w:800 x h:500 across browser sessions, but Value 3.0 causes the inner and outer windows, inner window content, and bookmarks folders and text in the Bookmarks Toolbar visible beneath the URL Address Bar to be excessively oversized, objectionably too large, and user unfriendly.

In contrast, modified Value 2.4 hits the sweet spot where all is good.

When versions 9.5.3, 9.5.1, and 9.5 are using modified Value 3.0 when the browser starts, and the user immediately sets modified Value 2.4, the window instantaneously displays screen resolution w:1000 x h:600, but only for that browser session, manually adjusting the window size correctly displays the screen resolution at a design multiple of w:50 x h:50, w:100 x h:100, or w:100 x h:200, but only for that session, and Enter Full Screen displays the screen at w:1200 x h:600, but only for that session.

Restarting 9.5.3, 9.5.1, and 9.5 while they are using modified Value 2.4 opens the window at screen resolution w:998 x h:599 across sessions, letterboxing incorrectly displays the window at screen resolutions w:348 x h:399 and w:798 x h:599 across sessions when adjusting the window size manually, and Enter Full Screen opens the window at w:1198 x h:599 across sessions.

In contrast, when versions 9.0.10, 9.0.9, and 9.0.4 are using modified Value 2.4 when they start, the window opens at screen resolution w:1000 x h:600 across browser sessions, letterboxing correctly displays the screen resolution only at some multiple of w:50 x h:50, w:50 x h:100, or w:100 x h:200 when manually adjusting the window size across sessions, and Enter Full Screen opens the window at screen resolution w:1200 x h:600 across sessions.

Can we fix this defect so that when Tor Browser is using modified configuration about:config > layout.css.devPixelsPerPx Value 2.4 when it starts, Tor Browser (1) opens the window at screen resolution w:1000 x h:600 across browser sessions, (2) letterboxing sets a correctly conforming multiple of screen resolution when manually adjusting window size across sessions, and (3) Enter Full Screen displays the screen resolution at w:1200 x h:600 across sessions?

Tor Browser versions 9.5.3, 9.5.1, 9.5, 9.0.10, 9.0.9, and 9.0.4 are using the following Customize settings in the screen resolution tests that prove the described observations:

(1) Customize... > Toolbars > ✓ Bookmarks Toolbar

(2) Customize... > Density > Compact

(3) Customize... > drag ★Bookmarks Toolbar Items into Bookmarks Toolbar

(4) Customize > Title Bar, Drag Space, and Themes are at their default settings.

Thank you

Anonymous

August 15, 2020

Permalink

Enterprise Policies are botched?

All Updates in Enterprise Policies are off but HTTSEverywhere tries downloading new rulesets?

Anonymous

August 17, 2020

Permalink

I was just in the middle of watching a video, and the video stopped and a yellow box showed up over the player. Then, I noticed the Noscript icon had a red line through it. My shield is on safer, and I had allowed media in Noscript which is how I was watching the video, but it's as if it was reset all of a sudden. Remembering older comments, I looked at Noscript's information in Add-ons, and it says it updated today to version 11.0.38. Did Noscript's update cause my video to stop playing? Because seeing my permissions suddenly change by themselves freaked me out.

Anonymous

August 20, 2020

Permalink

TypeError: aBrowser is null SessionStore.jsm:1159:9
updateSessionStoreFromTablistener resource:///modules/sessionstore/SessionStore.jsm:1159
updateSessionStoreFromTablistener resource:///modules/sessionstore/SessionStore.jsm:443
SSF_updateSessionStore resource://gre/modules/SessionStoreFunctions.jsm:441
UpdateSessionStore resource://gre/modules/SessionStoreFunctions.jsm:19