Skip to content

feat: add Chrome 152 TLS fingerprint and multi-platform release - #1

Closed
xiaoweigege wants to merge 1 commit into
jawah:mainfrom
xiaoweigege:feat/chrome-152
Closed

xiaoweigege wants to merge 1 commit into
jawah:mainfrom
xiaoweigege:feat/chrome-152

Conversation

@xiaoweigege

Copy link
Copy Markdown
Contributor

Chrome 152 sends trust_anchors (0xCA34) and GREASE in signature_algorithms. Compile BoringSSL from vendor/boringssl so SSL_CTX_set_grease_sigalgs_enabled is available. CI fetches the submodule and, on tags, uploads wheels to GitHub Releases. Forks skip PyPI because the utls name is taken by upstream.

Chrome 152 sends trust_anchors (0xCA34) and GREASE in
signature_algorithms. Compile BoringSSL from vendor/boringssl so
SSL_CTX_set_grease_sigalgs_enabled is available. CI fetches the
submodule and, on tags, uploads wheels to GitHub Releases. Forks skip
PyPI because the utls name is taken by upstream.
@xiaoweigege xiaoweigege closed this Sep 4, 2026
@Ousret

Ousret commented Sep 6, 2026

Copy link
Copy Markdown
Member

why not contribute?
...

@xiaoweigege

Copy link
Copy Markdown
Contributor Author

为什么不贡献一份力量呢 ?

The code generated by AI has flaws.

@Ousret

Ousret commented Sep 6, 2026

Copy link
Copy Markdown
Member

ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants