{"version":"2.1.323","anchor":"private-key-redaction-handles-already-redacted-markers","canonical_anchor":"private-key-redaction-handles-already-redacted-markers","heading":"Private-key hiding now catches keys whose edges were already hidden","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/private-key-redaction-handles-already-redacted-markers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Private-key hiding now catches keys whose edges were already hidden\n\nPrivate-key blocks are now recognized and hidden even when their BEGIN or END line was already replaced by a redaction marker\n\n**What**\n\nClaude Code hides private keys (secret cryptographic keys, written as a block of text between a BEGIN PRIVATE KEY line and an END PRIVATE KEY line) when they appear in text it handles. It previously recognized such a block only when both of those lines were present word for word.\n\nIt now also recognizes a block where the BEGIN or END line has already been replaced by a `[REDACTED...]` marker. The overlapping pieces are then treated as one block and hidden together.\n\n**Why**\n\nA key whose first or last line had already been hidden could slip past the check and leave the rest of the key visible. This closes that gap and helps keep keys out of logs.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}