New Release: Tor Browser 8.0

 

Update (09/07 10:15 UTC): We received reports of Tor Browser 8.0 crashing during start-up on older (10.9.x) macOS systems. This is tracked in bug 27482. The current Tor stable version, 0.3.3.9, is missing a patch to make it compatible with that old and unsupported (by Apple) macOS version. This will be fixed in the planned Tor Browser 8.0.1 release. Meanwhile, users affected by this bug can try the almost identical alpha release, 8.5a1, which is shipping a newer Tor version with this bug fixed. Sorry for the inconvenience.

For the past year, we have been collecting feedback on how we can make Tor Browser work better for you.

Tor Browser 8.0, our first stable release based on Firefox 60 ESR, is now available from the Tor Browser Project page and also from our distribution directory. This release is all about users first.

Tor Browser 8.0 comes with a series of user experience improvements that address a set of long-term Tor Browser issues you’ve told us about. To meet our users' needs, Tor Browser has a new user onboarding experience; an updated landing page that follows our styleguide; additional language support; and new behaviors for bridge fetching, displaying a circuit, and visiting .onion sites.

New User Onboarding

For the most part, using Tor is like using any other browser (and it is based on Firefox), but there are some usage differences and cool things happening behind the scenes that users should be aware of. Our new onboarding experience aims to better let you know about unique aspects of Tor Browser and how to maximize those for your best browsing experience.

Improved Bridge Fetching

For users where Tor is blocked, we have previously offered a handful of bridges in the browser to bypass censorship. But to receive additional bridges, you had to send an email or visit a website, which posed a set of problems. To simplify how you request bridges, we now have a new bridge configuration flow when you when you launch Tor. Now all you have to do is solve a captcha in Tor Launcher, and you’ll get a bridge IP. We hope this simplification will allow more people to bypass censorship and browse the internet freely and privately.

Better Language Support

Millions of people around the world use Tor, but not everyone has been able to use Tor in their language. In Tor Browser 8, we’ve added resources and support for nine previously unsupported languages: Catalan, Irish, Indonesian, Icelandic, Norwegian, Danish, Hebrew, Swedish, and Traditional Chinese.

Apart from those highlights, a number of other component and toolchains got an update for this major release. In particular, we now ship Tor 0.3.3.9 with OpenSSL 1.0.2p and Libevent 2.1.8. Moreover, we switched to the pure WebExtension version of NoScript (version 10.1.9.1) which we still need to provide the security slider functionality. Additionally, we start shipping 64bit builds for Windows users which should enhance Tor Browser stability compared to the 32bit bundles.

Providing this many improvements for our users could only be possible with collaboration between the Tor Browser team and Tor's UX team, Community team, Services Admin team, and our volunteers. We would like to thank everyone for working hard over the past year to bring all these new features to our users.

Known Issues

We already collected a number of unresolved bugs since Tor Browser 7.5.6 and tagged them with our ff60-esr keyword to keep them on our radar. The most important ones are listed below:

  • WebGL is broken right now.
  • We disable Stylo on macOS due to reproducibility issues we need to investigate and fix. This will likely not get fixed for Tor Browser 8, as we need some baking time on our nightly/alpha channel before we are sure there are no reproducibility/stability regressions. The tentative plan is to get it ready for Tor Browser 8.5.

 

Note: This release is signed with a new GPG subkey as the old one expired a couple of days ago. You might need to refresh your copy of the public part of the Tor Browser signing key before doing the verification. The fingerprint of the new subkey is 1107 75B5 D101 FB36 BC6C 911B EB77 4491 D9FF 06E2.

Give Feedback

This is only the beginning of our efforts to put users first. If you find a bug or have a suggestion for how we could improve this release, please let us know.

Changelog

The full changelog since Tor Browser 7.5.6 is:

  • All platforms
    • Update Firefox to 60.2.0esr
    • Update Tor to 0.3.3.9
    • Update OpenSSL to 1.0.2p
    • Update Libevent to 2.1.8
    • Update Torbutton to 2.0.6
      • Bug 26960: Implement new about:tor start page
      • Bug 26961: Implement new user onboarding
      • Bug 26962: Circuit display onboarding
      • Bug 27301: Improve about:tor behavior and appearance
      • Bug 27214: Improve the onboarding text
      • Bug 26321: Move 'New Identity', 'New Circuit' to File, hamburger menus
      • Bug 26100: Adapt Torbutton to Firefox 60 ESR
      • Bug 26520: Fix sec slider/NoScript for TOR_SKIP_LAUNCH=1
      • Bug 27401: Start listening for NoScript before it loads
      • Bug 26430: New Torbutton icon
      • Bug 24309: Move circuit display to the identity popup
      • Bug 26884: Use Torbutton to provide security slider on mobile
      • Bug 26128: Adapt security slider to the WebExtensions version of NoScript
      • Bug 27276: Adapt to new NoScript messaging protocol
      • Bug 23247: Show security state of .onions
      • Bug 26129: Show our about:tor page on startup
      • Bug 26235: Hide new unusable items from help menu
      • Bug 26058: Remove workaround for hiding 'sign in to sync' button
      • Bug 26590: Use new svg.disabled pref in security slider
      • Bug 26655: Adjust color and size of onion button
      • Bug 26500: Reposition circuit display relay icon for RTL locales
      • Bug 26409: Remove spoofed locale implementation
      • Bug 26189: Remove content-policy.js
      • Bug 26490: Remove the security slider notification
      • Bug 25126: Make about:tor layout responsive
      • Bug 27097: Add text for Tor News signup widget
      • Bug 21245: Add da translation to Torbutton and keep track of it
      • Bug 27129+20628: Add locales ca, ga, id, is, nb, da, he, sv, and zh-TW
      • Translations update
    • Update Tor Launcher to 0.2.16.3
      • Bug 23136: Moat integration (fetch bridges for the user)
      • Bug 25750: Update Tor Launcher to make it compatible with Firefox 60 ESR
      • Bug 26985: Help button icons missing
      • Bug 25509: Improve the proxy help text
      • Bug 26466: Remove sv-SE from tracking for releases
      • Bug 27129+20628: Add locales ca, ga, id, is, nb, da, he, sv, and zh-TW
      • Translations update
    • Update HTTPS Everywhere to 2018.8.22
    • Update NoScript to 10.1.9.1
    • Update meek to 0.31
      • Bug 26477: Make meek extension compatible with ESR 60
    • Update obfs4proxy to v0.0.7 (bug 25356)
    • Bug 27082: Enable a limited UITour for user onboarding
    • Bug 26961: New user onboarding
    • Bug 26962: New feature onboarding
    • Bug 27403: The onboarding bubble is not always displayed
    • Bug 27283: Fix first-party isolation for UI tour
    • Bug 27213: Update about:tbupdate to new (about:tor) layout
    • Bug 14952+24553: Enable HTTP2 and AltSvc
      • Bug 25735: Tor Browser stalls while loading Facebook login page
    • Bug 17252: Enable TLS session identifiers with first-party isolation
    • Bug 26353: Prevent speculative connects that violate first-party isolation
    • Bug 26670: Make canvas permission prompt respect first-party isolation
    • Bug 24056: Use en-US strings in HTML forms if locale is spoofed to english
    • Bug 26456: HTTP .onion sites inherit previous page's certificate information
    • Bug 26561: .onion images are not displayed
    • Bug 26321: Move 'New Identity', 'New Circuit' to File, hamburger menus
    • Bug 26833: Backport Mozilla's bug 1473247
    • Bug 26628: Backport Mozilla's bug 1470156
    • Bug 26237: Clean up toolbar for ESR60-based Tor Browser
    • Bug 26519: Avoid Firefox icons in ESR60
    • Bug 26039: Load our preferences that modify extensions (fixup)
    • Bug 26515: Update Tor Browser blog post URLs
    • Bug 26216: Fix broken MAR file generation
    • Bug 26409: Remove spoofed locale implementation
    • Bug 25543: Rebase Tor Browser patches for ESR60
    • Bug 23247: Show security state of .onions
    • Bug 26039: Load our preferences that modify extensions
    • Bug 17965: Isolate HPKP and HSTS to URL bar domain
    • Bug 21787: Spoof en-US for date picker
    • Bug 21607: Disable WebVR for now until it is properly audited
    • Bug 21549: Disable wasm for now until it is properly audited
    • Bug 26614: Disable Web Authentication API until it is properly audited
    • Bug 27281: Enable Reader View mode again
    • Bug 26114: Don't expose navigator.mozAddonManager to websites
    • Bug 21850: Update about:tbupdate handling for e10s
    • Bug 26048: Fix potentially confusing "restart to update" message
    • Bug 27221: Purge startup cache if Tor Browser version changed
    • Bug 26049: Reduce delay for showing update prompt to 1 hour
    • Bug 26365: Add potential AltSvc support
    • Bug 9145: Fix broken hardware acceleration on Windows and enable it
    • Bug 26045: Add new MAR signing keys
    • Bug 25215: Revert bug 18619 (we are not disabling IndexedDB any longer)
    • Bug 19910: Rip out optimistic data socks handshake variant (#3875)
    • Bug 22564: Hide Firefox Sync
    • Bug 25090: Disable updater telemetry
    • Bug 26127: Make sure Torbutton and Tor Launcher are not treated as legacy extensions
    • Bug 13575: Disable randomised Firefox HTTP cache decay user tests
    • Bug 22548: Firefox downgrades VP9 videos to VP8 for some users
    • Bug 24995: Include git hash in tor --version
    • Bug 27268+27257+27262+26603 : Preferences clean-up
    • Bug 26073: Migrate general.useragent.locale to intl.locale.requested
    • Bug 27129+20628: Make Tor Browser available in ca, ga, id, is, nb, da, he, sv, and zh-TW
      • Bug 12927: Include Hebrew translation into Tor Browser
      • Bug 21245: Add danish (da) translation
  • Windows
    • Bug 20636+10026: Create 64bit Tor Browser for Windows
      • Bug 26239+24197: Enable content sandboxing for 64bit Windows builds
      • Bug 26514: Fix intermittent updater failures on Win64 (Error 19)
      • Bug 26874: Fix UNC path restrictions failure in Tor Browser 8.0a9
      • Bug 12968: Enable HEASLR in Windows x86_64 builds
    • Bug 26381: Work around endless loop during page load and about:tor not loading
    • Bug 27411: Fix broken security slider and NoScript interaction on Windows
    • Bug 22581: Fix shutdown crash
    • Bug 25266: PT config should include full names of executable files
    • Bug 26304: Update zlib to version 1.2.11
    • Update tbb-windows-installer to 0.4
      • Bug 26355: Update tbb-windows-installer to check for Windows7+
    • Bug 26355: Require Windows7+ for updates to Tor Browser 8
  • OS X
    • Bug 24136: After loading file:// URLs clicking on links is broken on OS X
    • Bug 24243: Tor Browser only renders HTML for local pages via file://
    • Bug 24263: Tor Browser does not run extension scripts if loaded via about:debugging
    • Bug 22794: Don't open AF_INET/AF_INET6 sockets when AF_LOCAL is configured
  • Linux
    • Bug 22794: Don't open AF_INET/AF_INET6 sockets when AF_LOCAL is configured
    • Bug 25485: Unbreak Tor Browser on systems with newer libstdc++
    • Bug 20866: Fix OpenGL software rendering on systems with newer libstdc++
    • Bug 26951+18022: Fix execdesktop argument passing
    • Bug 24136: After loading file:// URLs clicking on links is broken on Linux
    • Bug 24243: Tor Browser only renders HTML for local pages via file://
    • Bug 24263: Tor Browser does not run extension scripts if loaded via about:debugging
    • Bug 20283: Tor Browser should run without a `/proc` filesystem.
    • Bug 26354: Set SSE2 support as minimal requirement for Tor Browser 8
  • Build System
    • All
      • Bug 26362+26410: Use old MAR format for first ESR60-based stable
      • Bug 27020: RBM build fails with runc version 1.0.1
      • Bug 26949: Use GitHub repository for STIX
      • Bug 26773: Add --verbose to the ./mach build flag for firefox
      • Bug 26319: Don't package up Tor Browser in the `mach package` step
      • Bug 27178: add support for xz compression in mar files
      • Clean up
    • Windows
      • Bug 26203: Adapt tor-browser-build/tor-browser for Windows
      • Bug 26204: Bundle d3dcompiler_47.dll for Tor Browser 8
      • Bug 26205: Don't build the uninstaller for Windows during Firefox compilation
      • Bug 26206: Ship pthread related dll where needed
      • Bug 26396: Build libwinpthread reproducible
      • Bug 25837: Integrate fxc2 into our build setup for Windows builds
      • Bug 27152: Use mozilla/fxc2.git for the fxc2 repository
      • Bug 25894: Get a rust cross-compiler for Windows
      • Bug 25554: Bump mingw-w64 version for ESR 60
      • Bug 23561: Fix nsis builds for Windows 64
        • Bug 13469: Windows installer is missing many languages from NSIS file
      • Bug 23231: Remove our STL Wrappers workaround for Windows 64bit
      • Bug 26370: Don't copy msvcr100.dll and libssp-0.dll twice
      • Bug 26476: Work around Tor Browser crashes due to fix for bug 1467041
      • Bug 18287: Use SHA-2 signature for Tor Browser setup executables
      • Bug 25420: Update GCC to 6.4.0
      • Bug 16472: Update Binutils to 2.26.1
      • Bug 20302: Fix FTE compilation for Windows with GCC 6.4.0
      • Bug 25111: Don't compile Yasm on our own anymore for Windows Tor Browser
      • Bug 18691: Switch Windows builds from precise to jessie
    • OS X
      • Bug 24632: Update macOS toolchain for ESR 60
      • Bug 9711: Build our own cctools for macOS cross-compilation
      • Bug 25548: Update macOS SDK for Tor Browser builds to 10.11
      • Bug 26003: Clean up our mozconfig-osx-x86_64 file
      • Bug 26195: Use new cctools in our macosx-toolchain project
      • Bug 25975: Get a rust cross-compiler for macOS
      • Bug 26475: Disable Stylo to make macOS build reproducible
      • Bug 26489: Fix .app directory name in tools/dmg2mar
    • Linux

Hm. I am not exactly sure how feeds are working here. But I guess feed updates go over the "catch-all" circuit given that there is no URL bar domain attached to them anymore once they are subscribed to. If that's the case we probably should be smarter than that and load the updates of different feeds over different circuits. You could check the behavior by looking at the Torbutton log output after setting extensions.torbutton.loglevel to 3 (it should be visible in the browser console; if you want to have the output in your terminal flip extensions.torbutton.logmethod to 0).

Okay, I opened https://trac.torproject.org/projects/tor/ticket/27633 for further investigation.

Seth Schoen

September 10, 2018

Permalink

How can we now prevent pages to reload themselves? This preference was removed with this release and I failed to find any about:config setting that would do the job, is there any?

When posting a comment, the page gets reloaded in a loop every couple of seconds, forever. Stopping and reloading manually does not help. I deleted the set of cookies, cache, active connexions and offline data, only then I could load the page normally again. Not sure if the comment was submitted, so I repeated, also after a fresh application restart and this appears reproducible (third time in two comments). This might be yet-another-unrelated-bug, but not being able to prevent automatic reloading is an issue (also) in this case.

I would regard this as a massive user experience regression, especially for with few hardware resources or little/unreliable bandwitch. Quite a few sites are abusing this "feature", e.g. to update the set of adverts they serve, or whatever other reason.

Same stand for NoScript automatic reloading after amending site preferences one way or another: until this release, it was possible to change them and not reload the page automatically, until we (the User) decided to reload the page whenever we see fit. This was also precious while disabling some permissions after contents had been fetched: terminating javascript execution, without loosing the resulting rendering.

This alone gives me a very frustrating UX on this release. :/

Thanks for forcing me to complete my homework :)

For NoScript itself, we had a clear option in the GUI and I think the preference was noscript.autoReload (default: true), I had that orphan setting in my profiles after upgrading. That functionality seems to have been entirely dropped: no GUI option, reload are now automatic when exiting the dynamic menu, if any permission was changed (no matter if added or removed).

For site refreshes on the Mozilla side, GUI option was under Accesibility and named "Warn me when websites try to redirect or reload the page". This one has been removed but the preference is still there and active, sorry: accessibility.blockautorefresh (default: false).

What happens is that it is less effective as the time goes. Feature itself may (?) have been limited to accomodate Google Translate or others, and/or more and more sites apparently use other techniques, even without javascript. Still effective with e.g. OpenWRT landings with luci-ssl, see also the test page linked below. Now helpless with e.g. Panopticlick redirects, your Drupal comment post bug here on Tor Blog, and too many sites to my taste.

Mozillazine: http://kb.mozillazine.org/Accessibility.blockautorefresh
GTranslate: https://bugzilla.mozilla.org/show_bug.cgi?id=1386910
Test page: http://www.searchtools.com/test/redirect/
Tutorial: https://techdows.com/2017/10/firefox-56-warn-me-when-websites-try-to-re…
Genesis: https://bugzilla.mozilla.org/show_bug.cgi?id=465303

I had tested various redirect blockers from AMO, had most of them disabled in one of my Firefox profiles, but they all appear obsolete since the WebExtensions move (didn't search again, just yet).

Seth Schoen

September 10, 2018

Permalink

no more search field and sites preview when open new tab.
search in config but cant find. no way to back it anymore?it was very useful..im cry..

Seth Schoen

September 10, 2018

Permalink

Good

Seth Schoen

September 10, 2018

Permalink

also i put browser.zoom.siteSpecific;true but it still reset sites zoom on shutdown...it very annoing.
so many new crazy settings, stay on ver7.5

Seth Schoen

September 10, 2018

Permalink

In Tor Browser 7.5.6, in the NoScript Options menu, when connected with blog.torproject.org, several options were available, including the following two options: (1) 'temporarily allow blog.torproject.org', (2) 'allow all on this page blog.torproject.org'. In Tor Browser 8.0, in the NoScript Options menu, (1) is no longer available; only (2) is available. Please restore (1) in NoScript options so I can select the option: 'temporarily allow blog.torproject.org'. I do not want to select 'allow all on this page blog.torproject.org'. I want to be able to select the option: 'temporarily allow blog.torproject.org'. Thanks

Seth Schoen

September 11, 2018

Permalink

Why the operating system is changing the user-agent in TBB8.0

Is this a Open Survey for which OS surfers use or to hard to programm a static user agent?

Add-on installs and configures just fine, but the mouse gestures do not work. No matter which mouse gesture I try, there's always a diagonal line (starting from the upper left corner to the center of the browser window) and then nothing happens.

Seth Schoen

September 11, 2018

Permalink

The TorBrowser team should look into replacing NoScript with ScriptSafe. It is basically feature equivalent to pre-webex NoScript and, I would say, even more user friendly (in comparison to Noscript's new textless interface which I found rather confusing). It is GPLv3. uMatrix is too finicky.

Seth Schoen

September 11, 2018

Permalink

How do you make NoScript disable JS by default like it was in the previous versions? Now it's allowed by default so I have to change it every time I start Tor, because the NoScript settings are reseted each time.

Seth Schoen

September 11, 2018

Permalink

The New Tor Browser 8 couldn't open the amazon.com website. The earlier version has no this problem, but it always forced my earlier version updated to new version which is pain in the ass.

Seth Schoen

September 11, 2018

Permalink

WTF men. I can't just see the pictures from the sankaku website! I think TOR now downloads pictures directly, that's the reason!

Seth Schoen

September 12, 2018

Permalink

The User Agent saga

I think I’ll abandon using Tor 8 and hope that when 8.0.1 is released the problem has been fixed.
After all, in your information about Tor 8 you say:

“For the past year, we have been collecting feedback on how we can make Tor Browser work better for you.” (Question. Who asked for the cessation of UA spoofing?)

“This release is all about users first.”

and

“This is only the beginning of our efforts to put users first (my italics). If you find a bug or have a suggestion for how we could improve this release, please let us know.

In view of the above and the comments on this blog, when is spoofing going to be put back, or is the comment made by one of the contributors of internal efforts to undermine the Tor project itself near the mark?

Thanks

Seth Schoen

September 12, 2018

Permalink

after sending a message to this blog TBB doesn't stop to reload.
new identity doesn't work:
Torbutton: Unexpected error on new identity: TypeError: m_tb_prefs is undefined

Seth Schoen

September 12, 2018

Permalink

Tbb is new installed, I want to import my bookmark backup file in .json formatted, after importing the Bookmark Toolbar showing in main window is still empty, but I can see every iterm from menu, why?

Seth Schoen

September 12, 2018

Permalink

noscript settings are messed up every launch and it remembers allowed scripts after new identity.

...it remembers allowed scripts after new identity...

THIS +1000

Also there's no way to limit the scope of a js to a site. Like if I enable google captcha on one site it is allowed everywhere. You should have invested the manpower that went into "interacting with the new noscript has been challenging" into replacing it with uMatrix.

Could someone from the Tor team comment on this please?

I enabled javascript for the hosts google captcha needs for some site.

After "the session" I revoked all temporary permissions in noscript (top right button in noscript menu", used "new identity" and on the first cloudflare site I hit after that google captchas were still working.

Seth Schoen

September 12, 2018

Permalink

What is default for cookies(Cookies and Site Data)?
Never/From visited/Always ?

There is no reset-to-default option in TBB8.0. Security slider don't set it to default.

Seth Schoen

September 12, 2018

Permalink

Hello, Thanks to all you guys developing this software and continue to support it. God Bless You.

I am trying to verify the signature for Tor Browser 8.0 but the signatures I am receiving do not match the signature output from your website.

https://www.torproject.org/docs/verifying-signatures.html
lists:
gpg: assuming signed data in 'torbrowser-install-8.0_en-US.exe'
gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET
gpg: using RSA key 0xD1483FA6C3C07136
gpg: Good signature from "Tor Browser Developers (signing key) " [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290
Subkey fingerprint: A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136

Currently valid subkey fingerprints are:

5242 013F 02AF C851 B1C7 36B8 7017 ADCE F65C 2036
BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0
A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136

I downloaded and verified the new keys from your keyserver and it listed pubkey correct in terminal but not subkey, im on linux fyi.
I downloaded your tor browser 8.0 file and the .asc sig.
My problem is when I verify:
gpg --verify tor-browser-linux64-8.0_en-US.tar.xz.asc
the output for the pub key is correct
but no valid sub key is found ( its not matching) based on your info on the website
https://www.torproject.org/docs/verifying-signatures.html
Any info would be helpful Thank you guys.

-MAGA

Seth Schoen

September 12, 2018

Permalink

The new NoScript is HORRIBLE, absolutely terrible. Unusable, the program is basically dead, as must be the brains of the developers. This was known already from the "normal" version, but is all the more apparent now that Tor uses it too.
Tor does not work now with this prorgram, which is a kind of bug and certainly a liability.

Seth Schoen

September 12, 2018

Permalink

Hello, your .asc sig file for linux tor browser 8.0 isnt matching the subkey when I verify
the package.
https://www.torproject.org/docs/verifying-signatures.html

gpg --keyserver pool.sks-keyservers.net --recv-keys 0x4E2C6E8793298290 -check
gpg --fingerprint 0x4E2C6E8793298290 -check
pub rsa4096/0x4E2C6E8793298290 2014-12-15 [C] [expires: 2020-08-24]
Key fingerprint = EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290 -check
gpg --verify tor-browser-linux64-8.0_en-US.tar.xz.asc -check
gpg: assuming signed data in 'tor-browser-linux64-8.0_en-US.tar.xz'
gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET
gpg: using RSA key 0xD1483FA6C3C07136 -Don't Match
gpg: Good signature from "Tor Browser Developers (signing key) " [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290 -check
Subkey fingerprint: A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136 -Dont Match
Currently valid subkey fingerprints are:

5242 013F 02AF C851 B1C7 36B8 7017 ADCE F65C 2036 -Don't Match
BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0 -Don't Match
A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136 -Don't Match

TorBrowser 8.0 Linux Downloaded from torproject.org
TorBrowser 8.0 asc file Downloaded from torproject.org

any reason why they dont match?

@gk
Tor's website @ https://www.torproject.org/docs/verifying-signatures.html
shows this:
" For Linux users (change 64 to 32 if you have the 32-bit package):

gpg --verify tor-browser-linux64-8.0_en-US.tar.xz.asc

The output should say "Good signature":

gpg: assuming signed data in 'tor-browser-linux64-8.0_en-US.tar.xz'
gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET
gpg: using RSA key 0xD1483FA6C3C07136
gpg: Good signature from "Tor Browser Developers (signing key) " [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290
Subkey fingerprint: A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136

Currently valid subkey fingerprints are:

5242 013F 02AF C851 B1C7 36B8 7017 ADCE F65C 2036
BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0
A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136 "

When I open Terminal and verify the package tor browser 8.0 linux along with the
tor browser 8.0 .asc file, the subkey fingerprints are not matching in my
terminal from what is listed @ Tor's website. None of the 3 valid subkey
fingerprints listed @ Tor's website is matching the output I get in Terminal.

example:(cant show you what key it lists or the rsa key( privacy concerns).

but I am giving you enough info for you to understand whats going on.

My Terminal info example:
gpg --verify tor-browser-linux64-8.0_en-US.tar.xz.asc
gpg: assuming signed data in 'tor-browser-linux64-8.0_en-US.tar.xz'
gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET (replace wed 15 nov 2017 with sep 2018 obviously)
gpg: using RSA key 0xD1483FA6C3C07136 (This RSAKEY Doesnt match mine)
gpg: Good signature from "Tor Browser Developers (signing key) " [unknown] (Matches mine)
gpg: WARNING: This key is not certified with a trusted signature! (Matches mine)
gpg: There is no indication that the signature belongs to the owner.(Matches Mine)
Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290 (Maches Mine)
Subkey fingerprint: A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136 ( Doesnt match my subkey)

Currently valid subkey fingerprints are:

5242 013F 02AF C851 B1C7 36B8 7017 ADCE F65C 2036 (Doesnt Match my subkey)
BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0 (Doesnt Match my subkey)
A430 0A6B C93C 0877 A445 1486 D148 3FA6 C3C0 7136 (Doesnt Match my subkey)

So either tor's webmaster @ https://www.torproject.org/docs/verifying-signatures.html
has not updated for the new keys tor released for tor browser 8.0 from this:

Quote from Tor release notes @ https://blog.torproject.org/new-release-tor-browser-80 below:

"Note: This release is signed with a new GPG subkey as the old one expired a couple of days ago. You might need to refresh your copy of the public part of the Tor Browser signing key before doing the verification. The fingerprint of the new subkey is 1107 75B5 D101 FB36 BC6C 911B EB77 4491 D9FF 06E2."

So When Tor is telling you to update your key ( yes Tor does infact have keys which u claimed u did not)
@ https://www.torproject.org/docs/verifying-signatures.html
Here is what that part of tor's website is telling you to do.

"The next step is to use GnuPG to import the key that signed
your package. The Tor Browser team signs Tor Browser releases. Import its
key (0x4E2C6E8793298290) by starting the terminal (under "Applications
in Mac OS X or Linux) and typing:

gpg --keyserver pool.sks-keyservers.net --recv-keys 0x4E2C6E8793298290"

Why are the keys not matching? RSA key and the 3 valid subkeys listed @
https://www.torproject.org/docs/verifying-signatures.html are not matching
the release of Tor Browser 8.0 Linux package downloaded from https://www.torproject.org

I hope that helps you understand more clearly @gk