TLS fingerprinting: How it works, where it is used and how to control your signature | lwt hiker
In this two-part series of posts I would like to expand about server-side browser fingerprinting. Server-side fingerprinting is a collection of techniques used by web servers to identify which web client is making a request based on network parameters sent by the client. By web client I mean the type of client, as in which browser or CLI tool, and not a specific user like what a cookie identifies.
In this two-part series of posts I would like to expand about server-side browser fingerprinting. Server-side fingerprinting is a collection of techniques used by web servers to identify which web client is making a request based on network parameters sent by the client. By web client I mean the type of client, as in which browser or CLI tool, and not a specific user like what a cookie identifies. A different technique from server-side fingerprinting is client-side fingerprinting, which is when Javascript is injected to test the client. This may be the subject of a future post, and I’ll focus
Explore this link on the map →saved by
related reading
- HTTP/2 fingerprinting: A relatively-unknown method for web fingerprinting | lwt hikerlwthiker.com
- The Illustrated TLS 1.3 Connection: Every Byte Explainedtls13.xargs.org
- TLS | Computer Securitytextbook.cs161.org
- Implementing a toy version of TLS 1.3jvns.ca
- Tailscale: How it workstailscale.com
- Themes from Real World Crypto 2022 - The Trail of Bits Blogblog.trailofbits.com
- Nascent.xyz | Crypto’s AirTag Moment: Unlocking Mass Adoption with Web Proofsnascent.xyz
- thesis.pdfaayushg.com
- Blocked by Cloudflarejrhawley.ca
- BREACH - Wikipediaen.wikipedia.org
- About HTTPS - FastAPIfastapi.tiangolo.com
- A Post-Quantum Future for Let's Encrypt - Let's Encryptletsencrypt.org