mirror of
https://github.com/Runnin4ik/dpi-detector.git
synced 2026-10-19 09:23:17 +00:00
3365c0da2c
curl-impersonate sends one hello for Chrome 133 through 146 — the same JA4, the same extension set and order distribution, the same h2 preface — so the rule in docs/ADDING_A_PROFILE.md keeps one record for the line, and `chrome133` is the single deliberate exception to it, recorded as such in the README, the guide and the harness's profile table. It exists to ask a question a run can answer: the two records differ only in `sec-ch-ua` and the `User-Agent`, neither of which is in the handshake, so a burst that presents both says whether the censor reads the identity or the hello. Measured on the three internal test-6 hosts, seven rounds each, interleaved: `chrome133` and `chrome146` answered identically in every round, while curl's own `chrome133a` — shuffling, under the flags its wrapper passes — finished its handshakes and uTLS's pinned `HelloChrome_133` was dropped: same version, same JA4, different extension order. The gates that pin the profile lists carry the new row: the ECH list, the shuffling list, the encoding table and the parse test, which no longer rejects `chrome133` now that the name resolves to the client it names. |
||
|---|---|---|
| .. | ||
| diag | ||
| fingerprint | ||