Repository navigation
chrome155/chrome156 profiles need Chrome's Trust Anchor IDs extension #588
Description
Since Chrome 152, every ClientHello carries the Trust Anchor IDs extension (0xca34) and a GREASE value first in signature_algorithms. apify/rustls can't send either, so a chrome155/156 profile can't match real Chrome's JA4 (it counts the extension).
I'd like to send a PR to apify/rustls adding both (and accepting a server's trust_anchors reply), then chrome155 and chrome156 profiles here. The profiles would list only the roots impit trusts, not Chrome's intermediates, so a server can't pick a chain impit can't verify.
Activity
barjin commentedon Oct 20, 2026
Sounds good, go ahead 👍 Fwiw, while you're in the rustls fork: Chrome for Testing 151 already sends an empty
0xca34plus two GREASE extensions (first one empty, last one a single byte), and ourchrome151sends neither, so feel free to fix that profile along the way.jackc625 commentedon Oct 20, 2026
Will do: I'll add the two GREASE extensions to apify/rustls#27, and update chrome151 (the empty
0xca34and both GREASE extensions) together with chrome155/156. The older Chrome profiles are short of them too (chrome124–142 send none, chrome100–116 one). Should I fix those as well, or keep it to chrome151?