Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Chrome/Firefox #2

Merged
merged 9 commits into from
Feb 28, 2019
Merged

Add support for Chrome/Firefox #2

merged 9 commits into from
Feb 28, 2019

Conversation

matogolf
Copy link
Contributor

No description provided.

@polcak polcak changed the title v0.1 ready Add support for Chrome/Firefox Feb 28, 2019
@polcak polcak merged commit 56b50b2 into polcak:master Feb 28, 2019
polcak added a commit that referenced this pull request Sep 15, 2021
* Add fingerprinting defenses based on Farbling developed by the Brave browser (improved or added
        wrappers for Canvas, Audio, Web GL, device memory, hardware concurrency, enumerateDevices). Most
        wrappers support provisioning of white lies that differ between origins and sessions (the
        fingeprint is different across origins and across sessions).
 * We claimed to generate white image fake Canvas value but instead generated fully transparent black image. We now generate the white image as it is more common in other anti-canvas fingerprinting tools (level 3).
 * toDataUrl() no longer destructs the original canvas.
* We use NoScript Commons Library to simplify some tasks like cross-browser support.
 * More reliable early content script configuration.
   * CSP headers no longer prevents the extension from wrapping JS APIs in Firefox (Github issue #25)
   * Wrappers should be injected reliably before page scripts start to operate (Github issue #40)
 * We use NSCL to wrap APIs in iframes and workers
   * It is no longer possible to access unwrapped functions from iframes and workers (Pagure issue #2, Github issue #56)
* Ignore trailing '.' in domain names when selecting appropriate custom level.
* Do not freeze wrappers to prevent fingeprintability of the users of JSR. We wrap the correct function
        in the prototype chain instead.
* navigator.getGamepads() wrapper added
* navigator.activeVRDisplays() and navigator.xr wrappers added
* Limit precision of high resolution timestamps in the Event, VRFrameData, and Gamepad interface to be consistent
        with Date and Performance precision
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants