1
0
mirror of https://github.com/niespodd/browser-fingerprinting.git synced 2021-11-01 22:44:07 +03:00

Update README.md

This commit is contained in:
niespodd
2021-02-13 08:31:22 +01:00
committed by GitHub
parent 1fd4d0ba5e
commit db32f21732

View File

@@ -42,7 +42,7 @@ A ⭐ on this repo will be **appreciated**!
## [Multilogin](https://multilogin.com), [Kameleo](https://kameleo.io/) and others 💰🤠
***General `navigator` and `window` properties** - As per [Multilogin documentation](https://docs.multilogin.com/l/en/article/chvo34br5c-global-browser-profile-preferences) custom browser builds typically lag behind the latest additions added by browser vendors - Chromium in this case.
***General `navigator` and `window` properties** - As per [Multilogin documentation](https://docs.multilogin.com/l/en/article/chvo34br5c-global-browser-profile-preferences) custom browser builds typically lag behind the latest additions added by browser vendors. In this case modified Chromium M7X is used (almost 10 versions behind when writing this).
* 🤷 **Font masking** - Font fingerprinting still leaks host OS due to use of [different font rendering backends on Win/Lin/Mac](https://blog.typekit.com/2010/10/15/type-rendering-operating-systems/). However, the basic "font whitelisting" technique can help to slightly rotate browser fingerprint.
***Inconsistencies** - Profile misconfiguration leads to early property/behavior inconsitency detection.
***Native extensions** - Unlike `puppeteer-extra-plugin-stealth` custom Chromium builds such as ML and Kameleo provide at most an override for native plugins and extensions shipped with Google Chrome.