blog.torproject.org
blog.torproject.org
blog.torproject.org
forum.torproject.net
forum.torproject.net
www.torproject.org
blog.torproject.org
blog.torproject.org
blog.torproject.org
blog.torproject.org
New release: Tor Browser 12.5
Tor Browser 12.5 is now available from the Tor Browser download page and our distribution directory. Many of the features in this release were made possible thanks to two projects:
Since 2021 we've provided digital security training to hundreds of journalists and human rights defenders in Brazil, Ecuador and Mexico alongside Guardian Project and Tails. During these workshops we documented pain points with our applications' user experience, and returned to validate potential solutions with Tor Browser Alpha in follow-up trips.
Secondly, in April we announced the launch of Mullvad Browser, a new privacy browser built by the Tor Project and distributed by Mullvad. This collaboration has enabled us to refactor Tor Browser's build system, address numerous legacy issues and conduct an accessibility review of Tor Browser's custom components – which you can learn more about below.
What's new?
Updated circuit display
In Tor Browser for desktop, the Tor circuit for each of your tabs can be found in the circuit display. Up until this release the circuit display lived in the site information panel – meaning you'd have to click the padlock icon (or onion icon, in the case of onion sites) to the left of the address bar to access it. Usability testing participants often struggled to find the circuit display when asked, and users generally needed to be taught where it lived.
To fix this, we've moved the circuit display behind a colorful new icon that sits beside the padlock. In addition, relays now have flags to help make their locations easier to identify at a glance; the design of onion site circuits has been made more concise; SecureDrop users who visit a human-readable onion name can now see and switch back to the underlying V3 onion address; and the panel as a whole has been rebuilt from scratch for better compatibility with screen readers.
New onion site icons
Previously, onion sites were represented by the onion-glyph – a tiny, flat version of Tor Browser's onion logo. Now, when you visit an onion site in Tor Browser 12.5 on either desktop or Android you'll notice something new.
It's important to recognize that onion services are not exclusive to Tor Browser, and are a product in their own right. As onion service adoption has grown among civil society groups, human rights organizations, and news media outlets, so too has support for visiting onion services by third-party apps. Today, in addition to Tor Browser, you can also access onion services in compatible apps like Orbot, Onion Browser and Brave, to name a few. Given that, it no longer makes sense to continue to represent onion sites with an icon so closely associated with Tor Browser, and we're excited to introduce their new identity today.
Improved connection experience
In Tor Browser 10.5 for desktop we retired the Tor Launcher in favor of a new interface that allows users to connect to Tor from the browser window itself. This feature unlocked the added benefit of being able to access Tor Browser's other menus while offline, including Connection settings, which offers greater functionality than the equivalent Tor Launcher settings page ever did.
Since that release, usability testing participants have sometimes had difficulty figuring out how to connect after navigating away from the Connect to Tor tab. To remedy this, we've made the Connect button accessible in the address bar of any page you visit while offline, and Tor Browser will connect automatically after you've configured a bridge in Connection settings. We've also improved the visibility of the browser's connection status, which can now be found in the top-right of the browser window, and you'll notice a new connection icon appear throughout the browser too.
Better accessibility
As Tor Browser is based on the Extended Support Release of Firefox, we reuse as much of Firefox's front-end user experience as possible so that we can concentrate our resources on privacy and security issues. However Tor Browser also includes many custom pages and components on top of Firefox.
In parallel with longstanding efforts by Mozilla to improve Firefox's accessibility, we began an accessibility review of our own to document issues with Tor Browser for desktop's custom features. This review has now been completed, and we're beginning to deploy the first fixes in what will be a multi-release effort to improve Tor Browser's accessibility.
Since Tor Browser 11.5 we've refactored several components including bundled changelogs (about:tbupdate), the circuit display, the security level panel, miscellaneous dialogs and other parts of the browser chrome. If you use a screen reader or any other assistive technology, we'd love to get your help testing past and future fixes by volunteering as an alpha tester and feeding back to our developers on the Tor forum.
blog.torproject.org
blog.torproject.org
blog.torproject.org
blog.torproject.org
blog.torproject.org
blog.torproject.org
blog.torproject.org
Tor Browser 13.0 is now available from the Tor Browser download page and our distribution directory.
This is our first stable release based on Firefox ESR 115, incorporating a year's worth of changes shipped upstream. As part of this process we've also completed our annual ESR transition audit, where we review Firefox's changelog for issues that may negatively affect the privacy and security of Tor Browser users and disable any problematic patches where necessary. Our final reports from this audit are now available in the tor-browser-spec repository on our Gitlab instance.
Particularly notable are the accessibility improvements we've gained as a result of the transition to Firefox ESR 115. While eagle-eyed users may notice small visual changes to the user interface (for example, internal links are now underlined), Tor Browser 13.0 is our first release to inherit the redesigned accessibility engine introduced by Mozilla in Firefox 113. This change promises to improve performance significantly for people who use screen readers and other assistive technology.
SourceWhat's new?
Refreshed application icons
Earlier this year we spent some time artworking the Mullvad Browser logo into the various assets needed to support its release – including application, installer and document icons that conform to each platform's conventions. While getting up to speed with the current requirements for each platform, we identified a number of gaps with Tor Browser too, and started working on new icons for Tor Browser in parallel.
For context, Tor Browser's current icon (sometimes referred to as the "onion logo") was selected by community poll over four years ago to succeed the older purple and green globe in Tor Browser 8.5. Given the community's involvement in its selection, its recognizability by netizens, and the simple fact that we still love the existing icon, we chose to focus on refining rather than replacing it entirely.
One of the motivations behind work like this is our philosophy that privacy-preserving products shouldn't be purely utilitarian, but can also spark joy. However there are practical benefits too: adhering to platform conventions provides better consistency, discernible application and installer icons help prevent user error, and attracting new users benefits everyone because anonymity loves company.
New homepage
For the past year we've been working on a significant rewrite of Tor Browser's back-end, which recently provided us with the opportunity to rebuild one of the few internal pages that hasn't changed in a while: the homepage (often referred to by its internal reference, "about:tor"). Tor Browser 13.0's homepage now features the new application icons, a simplified design, and the ability to "onionize" your DuckDuckGo searches by switching to the DuckDuckGo onion site. Continuing the work that began in Tor Browser 12.5 to improve the browser's accessibility, the redesigned homepage also offers better support for users of screen readers and other assistive technology too.
Existing Tor Browser users can rejoice that the "red screen of death" – an infamous error state that the previous homepage would occasionally trip itself into – is long gone. As part of the back-end rewrite we've removed the automatic Tor network connectivity check that was a hold-over from the legacy tor-launcher, where bootstrapping was handled by an extension that ran before the browser interface appeared. As a result of the tighter tor integration and in-browser bootstrapping experience introduced in Tor Browser 10.5, the old logic behind this check would often fail and present some users with the red screen of death, even if their connection was fine.
In fact, all of the reports we've received of users hitting this screen with the default tor configuration since Tor Browser 10.5 have proven to be false positives, causing undue alarm. Although the check is arguably still useful for users running non-default configurations, neither of the main environments which do so – Tails and Whonix – use about:tor as their default new-tab or home pages. For everyone else, we've added a new banner to the redesigned homepage in place of the red screen of death to check that tor is connected and working as expected.
Bigger new windows
The explanation for how and why Tor Browser works this way is going to get into the weeds a little, so be warned. However the main thing to take away is that new windows should be bigger by default and present themselves in a more useful landscape aspect-ratio for the majority of desktop users in Tor Browser 13.0. Now, about those weeds...
Letterboxing was introduced in Tor Browser 9.0 to allow users to resize their browser window without fear of being fingerprinted by rounding the inner content window (sometimes referred to as the "viewport") down to multiples of 200 x 100 pixels. This technique works by grouping the window sizes of most users into a series of common "buckets", protecting individual users within those buckets from being singled-out based on their window or screen size.
In order to preserve these protections when opening new windows, Tor Browser overrides platform defaults and will instead select a size that conforms to our letterboxing steps up to a maximum of 1000 x 1000 pixels. However, while that may have been fine in the past, a max width of 1000px is no longer suitable for the modern web. For example, on many newer websites the first responsive break point lies somewhere in the range of 1000 – 1200px, meaning by default Tor Browser users would receive website menus and layouts intended for tablet and mobile devices. Alternatively, on certain websites, users would receive the desktop version but with the annoyance of a horizontal scroll bar instead. This, naturally, would lead to users of these websites needing to expand each new window manually before it's usable.
In response we've bumped up the max size of new windows up to 1400 x 900 pixels and amended the letterboxing steps to match. Thanks to the increase in width, Tor Browser for desktop should no longer trigger responsive break points on larger screens and the vast majority of our desktop users will see a familiar landscape aspect-ratio more in-keeping with modern browsers. This particular size was chosen by crunching the numbers to offer greater real estate for new windows without increasing the number of buckets past the point of their usefulness. As an added bonus, we also expect that Tor Browser users will not feel the need to manually change their window size as frequently as before – thereby keeping more users aligned to the default buckets.
Technical notes
We're pleased to report that we've made the naming scheme for all our build outputs mutually consistent. Essentially, this means that going forward the names of all our build artifacts should follow the format ${ARTIFACT}-${OS}-${ARCH}-${VERSION}.${EXT}. For example, the macOS .dmg package for 12.5 was named TorBrowser-12.5-macos_ALL.dmg, whereas for 13.0 it's named tor-browser-macos-13.0.dmg.
If you are a downstream packager or download Tor Browser artifacts using scripts or automation, you'll need to do a little more work beyond just bumping the version number to support this and future releases.
Contributions
Thanks to all of the teams across Tor, and the wider community, who contributed to this release. In particular we'd like to extend our gratitude to the following volunteers who have contributed their expertise, labour, and time to this release:
- anonym
- cypherpunks1
- Fabrizio
- FlexFoot
- guest475646844
- honorton
- ilf
- JeremyRand
- nervuri
- Rusty Bird
- shanzhanz
- thorin
- trinity-1686a
Send us your feedback
If you find a bug or have a suggestion for how we could improve this release, please let us know.
Full changelog
The full changelog since Tor Browser 12.5.6 is:
- All Platforms
- Updated tor to 0.4.8.7
- Updated OpenSSL to 3.0.11
- Bug tor-browser-spec#40050: FF103 Audit
- Bug tor-browser-spec#40051: FF104 Audit
- Bug tor-browser-spec#40052: FF105 Audit
- Bug tor-browser-spec#40053: FF106 Audit
- Bug tor-browser-spec#40054: FF107 Audit
- Bug tor-browser-spec#40055: FF108 Audit
- Bug tor-browser-spec#40056: FF109 Audit
- Bug tor-browser-spec#40057: FF110 Audit
- Bug tor-browser-spec#40058: FF111 Audit
- Bug tor-browser-spec#40059: FF112 Audit
- Bug tor-browser-spec#40060: FF113 Audit
- Bug tor-browser-spec#40061: FF114 Audit
- Bug tor-browser-spec#40062: FF115 Audit
- Bug tor-browser#26277: When "Safest" setting is enabled searching using duckduckgo should always use the Non-Javascript site for searches
- Bug tor-browser#40577: Add "suggest url" in DDG onion's manifest
- Bug tor-browser#40938: Migrate remaining torbutton functionality to tor-browser
- Bug tor-browser#41092: Enable tracking query parameters stripping
- Bug tor-browser#41327: Disable UrlbarProviderInterventions
- Bug tor-browser#41399: Update Mozilla's patch for Bug 1675054 to enable brotli encoding for HTTP onions as well
- Bug tor-browser#41477: Review some extensions.* preferences
- Bug tor-browser#41496: Review 000-tor-browser.js and 001-base-profile.js for 115
- Bug tor-browser#41576: ESR115: ensure no remote calls for weather & addon suggestions
- Bug tor-browser#41605: Remove unused assets from torbutton (preferences-mobile.css)
- Bug tor-browser#41675: Remove javascript.options.large_arraybuffers
- Bug tor-browser#41727: WebRTC privacy-hardening settings
- Bug tor-browser#41740: ESR115: change devicePixelRatio spoof to 2 in alpha for testing
- Bug tor-browser#41752: Review changes done by Bug 41565
- Bug tor-browser#41796: Rebase Tor Browser to Firefox 115
- Bug tor-browser#41797: Lock RFP in release builds
- Bug tor-browser#41934: Websocket raises DOMException on http onions in 13.0a1
- Bug tor-browser#41936: Review Mozilla 1770158: Use double-conversion library instead of dtoa for string-to-double conversion
- Bug tor-browser#41937: Review Mozilla 1780014: Add specific telemetry for conservative and first-try handshakes
- Bug tor-browser#41938: Review Mozilla 1769994: On systems with IPv6 preferred DNS resolution clients will fail to connect when "localhost" is used as host for the WebSocket server
- Bug tor-browser#41939: Review Mozilla 1728871: Support fetching data from Remote Setting
- Bug tor-browser#41941: Review Mozilla 1775254: Improve Math.pow accuracy for large exponents
- Bug tor-browser#41943: Lock javascript.options.spectre.disable_for_isolated_content to false
- Bug tor-browser#41945: Review Mozilla 1783019: Add a cookie banner service to automatically handle website cookie banners
- Bug tor-browser#41946: Review Mozilla 1782579: Add a locale parameter to the text recognition API
- Bug tor-browser#41947: Review Mozilla 1779005: Broken since Firefox 102.0: no instant fallback to direct connection when proxy became unreachable while runtime
- Bug tor-browser#41950: Review Mozilla 1788668: Add the possibility to check that the clipboard contains some pdfjs stuff
- Bug tor-browser#41951: Review Mozilla 1790681: Enable separatePrivateDefault by default
- Bug tor-browser#41959: Review Mozilla 1795944: Remove descriptionheightworkaround
- Bug tor-browser#41960: Review Mozilla 1797896: Proxy environment variables should be upper case / case insensitive
- Bug tor-browser#41961: Review Mozilla 1798868: Hide cookie banner handling UI by default
- Bug tor-browser#41969: Review Mozilla 1746983: Re-enable pingsender2
- Bug tor-browser#41970: Review Mozilla 17909270: WebRTC bypasses Network settings & proxy.onRequest
- Bug tor-browser#41984: Rename languageNotification.ftl to base-browser.ftl
- Bug tor-browser#42013: Review Mozilla 1834374: Do not call EmptyClipboard() in nsBaseClipboard destructor
- Bug tor-browser#42014: Review Mozilla 1832791: Implement a Remote Settings for the Quarantined Domains pref
- Bug tor-browser#42015: Review Mozilla 1830890: Keep a history window of WebRTC stats for about:webrtc
- Bug tor-browser#42019: Empty browser's clipboard on browser shutdown
- Bug tor-browser#42026: Disable cookie banner service and UI.
- Bug tor-browser#42029: Defense-in-depth: disable non-proxied UDP WebRTC
- Bug tor-browser#42034: aboutTBUpdate.dtd is duplicated
- Bug tor-browser#42043: Disable gUM: media.devices.enumerate.legacy.enabled
- Bug tor-browser#42061: Move the alpha update channel creation to a commit on its own
- Bug tor-browser#42084: Race condition with language preferences may make spoof_english ineffective
- Bug tor-browser#42085: NEWNYM signal missing on Whonix
- Bug tor-browser#42094: Disable media.aboutwebrtc.hist.enabled as security in-depth
- Bug tor-browser#42120: Use foursquare as domain front for snowflake
- Bug tor-browser-build#40887: Update Webtunnel version to 38eb5505
- Windows + macOS + Linux
- Updated Firefox to 115.3.1esr
- Bug tor-browser#30556: Re-evaluate letterboxing dimension choices
- Bug tor-browser#32328: Improve error recovery from the red screen of death
- Bug tor-browser#33282: Increase the max width of new windows
- Bug tor-browser#33955: Selecting "Copy image" from menu leaks the source URL to the clipboard. This data is often dereferenced by other applications.
- Bug tor-browser#40175: Connections in reader mode are not FPI
- Bug tor-browser#40982: Cleanup maps in tor-circuit-display
- Bug tor-browser#40983: Move not UI-related torbutton.js code to modules
- Bug tor-browser#41165: Crash with debug assertions enabled
- Bug tor-browser#41333: Modernize Tor Browser's new-tab page (about:tor)
- Bug tor-browser#41423: about:tor semantic and accessibility problems
- Bug tor-browser#41528: Hard-coded English "based on Mozilla Firefox" appears in version in "About" dialog
- Bug tor-browser#41581: ESR115: figure out extension pinning / unified Extensions
- Bug tor-browser#41639: Fix the wordmark (title and background) of the "About Tor Browser" window
- Bug tor-browser#41642: Do not hide new PBM in the hamburger menu if auto PBM is not enabled
- Bug tor-browser#41651: Use moz-toggle in connection preferences
- Bug tor-browser#41691: "Firefox Suggest" text appearing in UI
- Bug tor-browser#41717: Bookmark toolbar visibility on new tabs is not honored when new tab page is not about:blank
- Bug tor-browser#41739: Remove "Website appearance"
- Bug tor-browser#41741: Refactor the domain isolator and new circuit
- Bug tor-browser#41765: TTP-02-006 WP1: Information leaks via custom homepage (Low)
- Bug tor-browser#41766: TTP-02-001 WP1: XSS in TorConnect's captive portal (Info)
- Bug tor-browser#41771: Decide what to do for firefoxview
- Bug tor-browser#41774: Hide the new "Switching to a new device" help menu item
- Bug tor-browser#41791: Copying page contents also puts the source URL on the clipboard
- Bug tor-browser#41812: Review layout for XUL elements
- Bug tor-browser#41813: Look out for links missing underlines in ESR 115-based alphas
- Bug tor-browser#41821: Fix the proxy type in the proxy modal of about
references in 13.0
- Bug tor-browser#41822: The default browser button came back on 115
- Bug tor-browser#41833: Reload extensions on new identity
- Bug tor-browser#41834: Hide "Can't Be Removed - learn more" menu line for uninstallable add-ons
- Bug tor-browser#41842: Remove the old removal logics from Torbutton
- Bug tor-browser#41844: Stop using the control port directly
- Bug tor-browser#41845: Stop forcing (bad) pref values for non-PBM users
- Bug tor-browser#41852: Review the Tor Check Service UX
- Bug tor-browser#41864: TOR_CONTROL_HOST and TOR_SOCKS_HOST do not work as expected when the browser launches tor
- Bug tor-browser#41865: Use --text-color-deemphasized rather than --panel-description-color
- Bug tor-browser#41874: Visual & A11 regressions in add-on badges
- Bug tor-browser#41876: Remove Firefox View from title bar
- Bug tor-browser#41877: NoScript seems to be blocking by default in the first 115-based testbuild
- Bug tor-browser#41881: Developer tools/Network/New Request remembers requests
- Bug tor-browser#41886: Downloads drop-down panel has new-line/line-break between every word in the 'Be careful opening downloads' warning
- Bug tor-browser#41904: The log textarea doesn't resize anymore
- Bug tor-browser#41906: Hide about
- Bug tor-browser#41907: The bootstrap is interrupted without any errors if the process becomes ready when already bootstrapping
- Bug tor-browser#41912: "Use Current Bridges" is shown for users even when there aren't any current bridges
- Bug tor-browser#41922: Unify the bridge line parsers
- Bug tor-browser#41923: The path normalization results in warnings
- Bug tor-browser#41924: Small refactors for TorProcess
- Bug tor-browser#41925: Remove the torbutton startup observer
- Bug tor-browser#41926: Refactor the control port client implementation
- Bug tor-browser#41931: Regression: new window leaks outer window
- Bug tor-browser#41935: Improve new window & letterboxing dimensions
- Bug tor-browser#41940: Review Mozilla 1739348: When a filetype is set to "always ask" and the user makes a save/open choice in the dialog, we should not also open the downloads panel
- Bug tor-browser#41949: Review Mozilla 1782578: Implement a context menu modal for text recognition
- Bug tor-browser#41954: Inputs in the request a bridge dialog are cut-off in 13.0 alpha
- Bug tor-browser#41957: Revert to Fx's default identity block style for internal pages
- Bug tor-browser#41958: Console error when closing tor browser with about
- Bug tor-browser#41964: emojiAnnotations not defined in time in connection preferences
- Bug tor-browser#41965: TorConnect error when opening browser tools
- Bug tor-browser#41971: Update Tails URL in downloads warning
- Bug tor-browser#41973: Custom wingpanels don't line up with their toolbar icons in 13.0 alpha
- Bug tor-browser#41974: De-emphasized text in custom components is no longer gray in 13.0 alpha
- Bug tor-browser#41975: Downloads warning text too narrow in 13.0 alpha
- Bug tor-browser#41976: Bottom padding on collapsed bridge cards has increased in 13.0 alpha
- Bug tor-browser#41977: Hide the "Learn more" link in bridge cards
- Bug tor-browser#41980: Circuit display headline is misaligned in 13.0 alpha
- Bug tor-browser#41981: Review Mozilla 1800675: Add about
- Bug tor-browser#41983: Review Mozilla 1770447: Create a reusable "support-link" widget
- Bug tor-browser#41986: Fix the control port password handling
- Bug tor-browser#41994: CSS (and other assets) of some websites blocked in 13.0 alpha
- Bug tor-browser#42022: Prevent extension search engines from breaking the whole search system
- Bug tor-browser#42027: Create a Base Browser version of migrateUI
- Bug tor-browser#42037: Disable about:firefoxview
- Bug tor-browser#42041: TBB --allow-remote mixes up with plain Firefox
- Bug tor-browser#42045: Circuit panel overflows with long ipv6 addresses
- Bug tor-browser#42046: Remove XUL layout hacks from base browser
- Bug tor-browser#42047: Remove layout hacks from tor browser preferences
- Bug tor-browser#42050: Bring back Save As... dialog as default
- Bug tor-browser#42073: Add simplified onion pattern to the new homepage
- Bug tor-browser#42075: Fix link spacing and underline on new homepage
- Bug tor-browser#42079: TorConnect: handle switching from Bootstrapped to Configuring state
- Bug tor-browser#42083: RemoteSecuritySettings.init throws error in console
- Bug tor-browser#42091: Onion authorization prompt overflows
- Bug tor-browser#42092: Onion services key table display problems.
- Bug tor-browser#42098: Implement Windows installer icons
- Bug tor-browser#42100: Connect Assist dropdown text not centered
- Bug tor-browser#42102: TorProcess says the SOCKS port is not valid even though it is
- Bug tor-browser#42109: Onion services keys table has empty column headers.
- Bug tor-browser#42110: Add a utility module for shared UI methods needed for several tor browser components
- Bug tor-browser#42126: moat and connect assist broken for people who can't reach domain front
- Bug tor-browser#42129: Disable the Tor restart prompt if shouldStartAndOwnTor is false
- Bug tor-browser#42131: Tor Browser 13.0a5 does not track circuits created before Tor Browser started
- Bug tor-browser#42132: The new control port handling in Tor Browser 13 breaks a Tails security feature
- Bug tor-browser#42138: Disable apz.overscroll.enabled pref
- Bug tor-browser#42155: Drop the unused code for the old bridge removal warning
- Bug tor-browser#42159: Responsive Design Mode not working correctly
- Bug tor-browser#42160: Allow specifying a TOR_PROVIDER=none to configure only the proxy settings during the TorProviderBuilder initialization
- Bug tor-browser#42166: New identity dialog missing accessible name
- Bug tor-browser#42167: Make the preference auto-focus more reliable
- Bug tor-browser-build#40821: The update details URL is wrong in alphas
- Bug tor-browser-build#40893: Update (Noto) fonts for 13.0
- Bug tor-browser-build#40924: Customize MOZ_APP_REMOTINGNAME instead of passing --name and --class
- Bug tor-browser-build#40938: Copy the new tor-browser.ftl file to the appropriate directory
- Windows + Android
- Bug tor-browser-build#40930: Upate zlib to 1.3 after 13.0a3
- Windows
- Bug tor-browser#40737: Revert backout of Mozilla's fix for bug 1724777
- Bug tor-browser#41658: Create new installer icons for Windows
- Bug tor-browser#41798: Stop building private_browsing.exe on Windows
- Bug tor-browser#41806: Prevent Private Browsing start menu item to be added automatically
- Bug tor-browser#41942: Review Mozilla 1682520: Use the WER runtime exception module to catch early crashes
- Bug tor-browser#41944: Review Mozilla 1774083: Add Surrogate COM Server to handle native Windows notifications when Firefox is closed.
- Bug tor-browser#42008: Review Mozilla 1808146: Copying images from Pixiv and pasting them in certain programs is broken
- Bug tor-browser#42010: Review Mozilla 1810641: Enable overscroll on Windows on all channels
- Bug tor-browser#42087: Implement Windows application icons
- Bug tor-browser-build#40954: Implement Windows installer icons
- macOS
- Bug tor-browser#41948: Review Mozilla 1782981: Hide the text recognition context menu if the macOS version doesn't support APIs
- Bug tor-browser#41955: Update macOS volume window background
- Bug tor-browser#41982: Review Mozilla 1762392: Add Cocoa platform support for paste files
- Bug tor-browser#42057: Disable Platform text-recognition functionality
- Bug tor-browser#42078: Implement MacOS application icons
- Bug tor-browser#42147: Add browser.helperApps.deleteTempFileOnExit to our profile
- Linux
- Bug tor-browser#41509: After update, KDE Plasma identifies Tor Browser Nightly window group as "firefox-nightly"
- Bug tor-browser#41884: Linux: set browser.tabs.searchclipboardfor.middleclick to false
- Bug tor-browser#42088: Implement Linux application icons
- Bug tor-browser-build#40576: Fontconfig warning: remove 'blank' configuration
- Android
- Updated GeckoView to 115.3.1esr
- Bug tor-browser#41878: firefox-mobile: refactor tor bootstrap off deleted onboarding path
- Bug tor-browser#41882: Update DuckDuckGo icons
- Bug tor-browser#41911: Firefox-Android tor bootstrap connect button css broken
- Bug tor-browser#41928: Backport Android-specific security fixes from Firefox 116 to ESR 102.14 / 115.1 - based Tor Browser
- Bug tor-browser#41972: Disable Firefox onboarding in 13.0
- Bug tor-browser#41990: Review Mozilla 1811531: Add 'site' query parameter to Pocket sponsored stories request
- Bug tor-browser#41991: Review Mozilla 1812518: Allow a custom View for 3rd party downloads
- Bug tor-browser#41993: Review Mozilla 1810761: Add API for saving a PDF
- Bug tor-browser#41996: App includes com.google.android.gms.permission.AD_ID permission
- Bug tor-browser#41997: com.adjust.sdk.Adjust library enables AD_ID permission even though we aren't using it
- Bug tor-browser#41999: TB13.0a2 android: center text on connect button
- Bug tor-browser#42001: Hide 'Open links in external app' settings option and force defaults
- Bug tor-browser#42002: Review Mozilla 1809305: Allow user to copy an image to the clipboard
- Bug tor-browser#42003: Review Mozilla 1819431: Reimplement default browser notification with Nimbus Messaging equivalent
- Bug tor-browser#42004: Review Mozilla 1818015: Use a custom tab or the view we use for Sync onboarding for the Privacy button
- Bug tor-browser#42005: Review Mozilla 1816932: Add Maps to app links common sub domains
- Bug tor-browser#42006: Review Mozilla 1817726: Allow sharing current tab URL from Android's Recents (App Overview) screen.
- Bug tor-browser#42007: Review Mozilla 1805450: Allow users to submit site support requests in Fenix
- Bug tor-browser#42012: Review Mozilla 1810629: add an Android shortcut to go straight to the login and passwords page
- Bug tor-browser#42016: Review Mozilla 1832069: Implement Google Play Referrer Library to fetch referrer URL
- Bug tor-browser#42018: Rebase Firefox for Android to 115.2.1
- Bug tor-browser#42023: Remove FF what's new from Android
- Bug tor-browser#42038: TBA Alpha - inscriptions Tor Browser Alpha and FireFox Browser simultaneously on the start screen
- Bug tor-browser#42074: YEC 2023 Takeover for Android Stable
- Bug tor-browser#42076: Theme is visible in options, but shouldn't be
- Bug tor-browser#42089: Disable the Cookie Banner Reduction site support requests (Mozilla 1805450)
- Bug tor-browser#42114: Disable Allow sharing current tab URL from Android's Recents screen in private browsing mode
- Bug tor-browser#42115: Enhanced Tracking Protection can still be enabled
- Bug tor-browser#42122: playstore console crashes: java.lang.NoSuchMethodError
- Bug tor-browser#42133: Remove "Total Cookie Protection" popup
- Bug tor-browser#42134: Remove Android icon shortcuts
- Bug tor-browser#42156: Screenshot allowing still blocks homescreen (android)
- Bug tor-browser#42157: Fix Help button URL
- Bug tor-browser#42165: Remove "Add to shortcuts" and "Remove from shortcuts" buttons
- Bug tor-browser#42158: Remove "Customize Homepage" button
- Bug tor-browser-build#40740: Tor Browser for Android's snowflake ClientTransportPlugin seems to be out of date
- Bug tor-browser-build#40919: Fix nimbus-fml reproducibility of 13.0a2-build1
- Bug tor-browser-build#40941: Remove PT process options on Android
- Build System
- All Platforms
- Updated Go to 1.21.1
- Bug tor-browser#42130: Add support for specifying the branch in tb-dev rebase-on-default
- Bug tor-browser-build#31588: Be smarter about vendoring for Rust projects
- Bug tor-browser-build#40089: Clean up usage of get-moz-build-date script
- Bug tor-browser-build#40410: Get rid of python2
- Bug tor-browser-build#40487: Bump Python version
- Bug tor-browser-build#40741: Update browser and tor-android-service projects to pull data from pt_config.json
- Bug tor-browser-build#40802: Drop the patch for making WASI reproducible
- Bug tor-browser-build#40829: Review and standardize naming scheme for browser installer/package artifacts
- Bug tor-browser-build#40854: Update to OpenSSL 3.0
- Bug tor-browser-build#40855: Update toolchains for Mozilla 115
- Bug tor-browser-build#40868: Bump Rust to 1.69.0
- Bug tor-browser-build#40880: The README doesn't include some dependencies needed for building incrementals
- Bug tor-browser-build#40886: Update README with instructions for Arch linux
- Bug tor-browser-build#40898: Add doc from tor-browser-spec/processes/ReleaseProcess to gitlab issue templates
- Bug tor-browser-build#40908: Enable the --enable-gpl config flag in tor to bring in PoW functionality
- Bug tor-browser-build#40929: Update go to 1.21 series after 13.0a3
- Bug tor-browser-build#40932: Remove appname_bundle_android, appname_bundle_macos, appname_bundle_linux, appname_bundle_win32, appname_bundle_win64 from projects/release/update_responses_config.yml
- Bug tor-browser-build#40935: Fix fallout from build target rename in signing scripts
- Bug tor-browser-build#40948: Remove lyrebird-vendor sha256sum in nightly
- Bug tor-browser-build#40957: Expired subkey warning on Tor Browser GPG verification
- Bug tor-browser-build#40972: Handle Mullvad Browser in the changelog script and group entries by project
- Windows + macOS + Linux
- Bug tor-browser#41967: Add a Makefile recipe to create multi-lingual dev builds
- Bug tor-browser-build#40149: Remove patching of nightly update URL
- Bug tor-browser-build#40615: Consider adding a readme to the fonts directory
- Bug tor-browser-build#40907: Sometimes debug information are not deterministic with Clang 16.0.4
- Bug tor-browser-build#40922: Use base-browser.ftl instead of languageNotification.ftl
- Bug tor-browser-build#40931: Fix incrementals after tor-browser-build#40829
- Bug tor-browser-build#40933: Fix generating incrementals between 12.5.x and 13.0
- Bug tor-browser-build#40942: Use the branch to build Base Browser
- Bug tor-browser-build#40944: After #40931, updates_responses is using incremental.mar files as if they were non-incremental mar files
- Bug tor-browser-build#40947: Remove migrate_langs from tools/signing/nightly/update-responses-base-config.yml
- Bug tor-browser-build#40956: Allow testing the updater also with release and alpha channel
- Windows
- Bug tor-browser#41995: Generated headers on Windows aren't reproducible
- Bug tor-browser-build#40832: Unify mingw-w64-clang 32+64 bits
- Bug tor-browser-build#40940: Change position of the install|portable in the builds filenames
- macOS
- Bug tor-browser#42035: Update tools/torbrowser/ scripts to support macOS dev environment
- Bug tor-browser-build#40943: Update libdmg-hfsplus to include our uplifted patch
- Bug tor-browser-build#40951: Firefox fails to build for macOS after tor-browser-build#40938
- Linux
- Bug tor-browser#42071: tor-browser deployed format changed breaking fetch.sh
- Bug tor-browser-build#40102: Move from Debian Jessie to Debian Stretch for our Linux builds
- Bug tor-browser-build#40971: Stop shipping Linux i686 debug archive until we actually produce the symbols
- Android
- Bug tor-browser#41899: Use LLD for Android
- Bug tor-browser-build#40867: Create a RBM project for the unified Android repository
- Bug tor-browser-build#40917: Remove the uniffi-rs project
- Bug tor-browser-build#40918: The commit hash is still not displayed about:buildconfig on Android
- Bug tor-browser-build#40920: Non-deterministic generation of baseline.profm file in Android apks
- Bug tor-browser-build#40963: Tor Browesr 13.0 torbrowser-testbuild-android* targets fail to build
- Bug tor-browser-build#40974: firefox-android fails to build in release
blog.torproject.org
blog.torproject.org
