geoffrey
/
eulaurarien
1
0
Vork 0
Code Kwesties 6 Pull-aanvragen Publicaties 1 Wiki Activiteit

README: Added more reasons the browsers trust first party

This commit is contained in:
Geoffrey Frogeye 2020-01-11 13:01:51 +01:00
bovenliggende 9326dc6aca
commit b09f861c27
Getekend door: geoffrey
GPG sleutel-ID: D8A7ECA00A8CD3DD
1 gewijzigde bestanden met toevoegingen van 2 en 2 verwijderingen
Statistieken weergeven Download Patch-bestand Download Diff-bestand Expand all files Collapse all files

4
dist/README.md vendored
Bestand weergeven

@ -14,8 +14,8 @@ However, to circumvent this block, tracker companies made the websites using the
The latter is a DNS redirection to `website1.trackercompany.com`, directly to an IP address belonging to the tracking company.
Those are called first-party trackers.
On top of aforementionned privacy issues, they also cause some security issue, as websites are usually configured to trust first-party scripts.
For more information, learn about [Cross-Origin Resource Sharing](https://enable-cors.org/).
On top of aforementionned privacy issues, they also cause some security issue, as websites usually trust those scripts more.
For more information, learn about [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP), [same-origin policy](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) and [Cross-Origin Resource Sharing](https://enable-cors.org/).
In order to block those trackers, ad blockers would need to block every subdomain pointing to anything under `trackercompany.com` or to their network.
Unfortunately, most don't support those blocking methods as they are not DNS-aware, e.g. they only see `somestring.website1.com`.