Claude Code v2.1.232 · 13 Aug 2026
Mismatched mTLS client certificate and key are ignored instead of installed
A mismatched client certificate and key pair is now ignored and logged instead of installed.
You'll notice Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
2 Signal: worth watching, 1 to 5
Internals Area: what it touches
Bug Fixes Kind: in v2.1.232, 13 Aug 26
Bug Fixes Section of the release
What
When CLAUDE_CODE_CLIENT_CERT and CLAUDE_CODE_CLIENT_KEY do not belong together, typically mid-rotation, the loader now logs "mTLS: Ignoring mismatched client cert/key pair" and keeps the previously loaded pair rather than installing a broken one.
Details
The pair is verified with Node's X509Certificate.checkPrivateKey, honouring CLAUDE_CODE_CLIENT_KEY_PASSPHRASE . Certificate blocks are located with a new PEM block pattern, so a bundle containing several certificates is handled. Evidence
mTLS: Ignoring mismatched client cert/key pair
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.232 →
13 Aug 2026 · 405 entries, this one is #276.
Use it now43 You'll notice209 Nothing to try yet41 Under the hood112
Open the release →
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 275 of 405
Truncated agent reports no longer point at a file that is not there
You'll notice Subagents
In v2.1.232 Bug Fixes release-page order
Next → · 277 of 405
A slow plugin read can no longer resurrect a cleared cache
You'll notice Plugins