bearbrowser: bump cask to v150.0.3 - #16
Merged
Merged
Conversation
Xray fix for the hardwareConcurrency clamp — verified on the actual DMG, runtime audit reports 2 instead of the real 8. Also carries the cockpit wiring (present-and-inert until CI assembles a cockpit).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v150.0.3 fixes the fingerprinting leak v150.0.2 shipped as known-open.
navigator.hardwareConcurrencyreturned the real CPU count in v150.0.2. In v150.0.3 it returns2, verified by runtime audit against the shipped DMG. Root cause was the Xray-wrapper interaction; the fix operates onwrappedJSObject+Cu.exportFunction.Also new: cockpit wiring is present but inert (CI does not assemble the cockpit yet), so the browser is bit-for-bit unaffected by that path in this release.
sha256 verified via
brew fetch-equivalent locally before publishing.