Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Gateway TLS pin mismatch names both certificates

You'll notice
Useful2 Signal2
Auth

A gateway certificate pin mismatch now shows both the presented and the trusted fingerprint.

What

When the cloud gateway presents a certificate that does not match the pinned fingerprint, the sign-in failure message can now name the fingerprint that was presented as well as the one that was trusted.

Details
  • Both fingerprints are attached to the thrown error, and a new extractor reads them off the error or its cause.
Evidence

gateway TLS certificate does not match the pinned fingerprint

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →