feat(cli): TLS/HTTP2 fingerprint hardening via tls-client #40

Merged

starkSV merged 2 commits from feat/cli-tls-fingerprint-hardening into main

2026-07-31 12:18:56 +05:30

starkSV commented

2026-07-31 12:17:53 +05:30

(Migrated from github.com)

Summary

Three checkpoints over 17 days confirmed a stable ~20% Sentinel rejection rate on the CLI's own requests, despite running from residential IPs specifically to avoid ASN-based blocking. That persistence points at TLS ClientHello fingerprinting as an additional signal -- Go's stdlib crypto/tls produces a handshake that looks nothing like a real browser, independent of IP or headers.
Swaps the CLI's HTTP transport from net/http to github.com/bogdanfinn/tls-client, which wraps utls with a maintained Chrome browser profile (TLS and HTTP2 fingerprint together).
Bumped msUA's claimed Chrome version to 133 to match the chosen TLS profile (Chrome_133) -- a mismatched UA vs. TLS fingerprint would be its own tell.
Removed the custom simpleCookieJar (tls-client provides its own). Applied the same client to fetchEvalLinks for consistency, even though Eval Center isn't currently blocked.
Also includes docs cleanup: PROGRESS.md/CLAUDE.md now document the full Sentinel WAF investigation saga (backend fixes already merged in #39, this CLI fix, and the still-unbuilt /needs-warming proposal). Retired two fully-shipped plan/spec docs under docs/superpowers/, and committed the previously-untracked needs-warming spec.

Test plan

go build ./..., go vet ./..., go test ./... all pass
Live end-to-end run (msdl --id 3262 --lang English) returned a real signed download link and successfully contributed it back to the shared cache
Live end-to-end run (msdl --eval server-2025) correctly fetched and listed real eval download options
Not provable pre-merge: this proves the flow works functionally through the new client, not that the fingerprint theory is correct -- the old client already succeeded ~80% of the time. Need to watch the Sentinel-rejection-rate telemetry over a comparable multi-day window after this ships to know if it actually moved.

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com

## Summary - Three checkpoints over 17 days confirmed a stable ~20% Sentinel rejection rate on the CLI's own requests, despite running from residential IPs specifically to avoid ASN-based blocking. That persistence points at TLS ClientHello fingerprinting as an additional signal -- Go's stdlib `crypto/tls` produces a handshake that looks nothing like a real browser, independent of IP or headers. - Swaps the CLI's HTTP transport from `net/http` to [`github.com/bogdanfinn/tls-client`](https://github.com/bogdanfinn/tls-client), which wraps `utls` with a maintained Chrome browser profile (TLS *and* HTTP2 fingerprint together). - Bumped `msUA`'s claimed Chrome version to 133 to match the chosen TLS profile (`Chrome_133`) -- a mismatched UA vs. TLS fingerprint would be its own tell. - Removed the custom `simpleCookieJar` (tls-client provides its own). Applied the same client to `fetchEvalLinks` for consistency, even though Eval Center isn't currently blocked. - Also includes docs cleanup: PROGRESS.md/CLAUDE.md now document the full Sentinel WAF investigation saga (backend fixes already merged in #39, this CLI fix, and the still-unbuilt `/needs-warming` proposal). Retired two fully-shipped plan/spec docs under `docs/superpowers/`, and committed the previously-untracked needs-warming spec. ## Test plan - [x] `go build ./...`, `go vet ./...`, `go test ./...` all pass - [x] Live end-to-end run (`msdl --id 3262 --lang English`) returned a real signed download link and successfully contributed it back to the shared cache - [x] Live end-to-end run (`msdl --eval server-2025`) correctly fetched and listed real eval download options - [ ] **Not provable pre-merge**: this proves the flow works functionally through the new client, not that the fingerprint theory is correct -- the old client already succeeded ~80% of the time. Need to watch the Sentinel-rejection-rate telemetry over a comparable multi-day window after this ships to know if it actually moved. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

coderabbitai[bot] commented

2026-07-31 12:34:14 +05:30

(Migrated from github.com)

Warning

Review limit reached

@starkSV, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 46f8fd68-67dc-4cfd-a4de-9f52d329521e

📥 Commits

Reviewing files that changed from the base of the PR and between 6ace2ceb19 and 78be837a4a.

⛔ Files ignored due to path filters (1)

cli/go.sum is excluded by !**/*.sum

📒 Files selected for processing (8)

CLAUDE.md

PROGRESS.md

cli/go.mod

cli/microsoft.go

docs/superpowers/plans/2026-06-15-msdl-cli.md

docs/superpowers/plans/2026-06-21-cli-telemetry-update-check.md

docs/superpowers/specs/2026-06-21-cli-telemetry-update-check-design.md

docs/superpowers/specs/2026-07-13-needs-warming-design.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

> [!WARNING] > ## Review limit reached > > `@starkSV`, you've reached your PR review limit, so we couldn't start this review. > > **Next review available in:** **2 minutes** > > Enable **[usage-based reviews](https://app.coderabbit.ai/settings/billing?tab=usage&orgId=47e9434f-e709-482d-ae08-cc95f1974bac)** in Billing to review now. Otherwise, wait until the next included review is available. > You're only billed for reviews past your plan's rate limits ($0.25/file). > > <details> > <summary>How can I continue?</summary> > > After more reviews become available, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. > > To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. > > </details> > > > <details> > <summary>How do review limits work?</summary> > > CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. > > For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. > > Please refer [docs](https://docs.coderabbit.ai/management/plans#rate-limits) for additional details. > > </details> > > <details> > <summary>Review details</summary> > > <details> > <summary>⚙️ Run configuration</summary> > > **Configuration used**: defaults > > **Review profile**: CHILL > > **Plan**: Pro Plus > > **Run ID**: `46f8fd68-67dc-4cfd-a4de-9f52d329521e` > > </details> > > <details> > <summary>📥 Commits</summary> > > Reviewing files that changed from the base of the PR and between 6ace2ceb199b3e7690cec1e8e6f7120fc45484f2 and 78be837a4a8049a27a20dfddb4c91b1485497c0d. > > </details> > > <details> > <summary>⛔ Files ignored due to path filters (1)</summary> > > * `cli/go.sum` is excluded by `!**/*.sum` > > </details> > > <details> > <summary>📒 Files selected for processing (8)</summary> > > * `CLAUDE.md` > * `PROGRESS.md` > * `cli/go.mod` > * `cli/microsoft.go` > * `docs/superpowers/plans/2026-06-15-msdl-cli.md` > * `docs/superpowers/plans/2026-06-21-cli-telemetry-update-check.md` > * `docs/superpowers/specs/2026-06-21-cli-telemetry-update-check-design.md` > * `docs/superpowers/specs/2026-07-13-needs-warming-design.md` > > </details> > > </details>   --- Thanks for using [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=starkSV/windows-iso-downloader&utm_content=40)! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. <details> <summary>❤️ Share</summary> - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code) </details> <sub>Comment `@coderabbitai help` to get the list of available commands.</sub>