{"version":"2.1.234","anchor":"secret-redaction-handles-private-keys-and-stops-firing-mid-w","canonical_anchor":"secret-redaction-handles-private-keys-and-stops-firing-mid-w","heading":"Secret redaction handles private keys and stops firing mid-word","tier":"notice","area":"Secret Redaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/secret-redaction-handles-private-keys-and-stops-firing-mid-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Secret redaction handles private keys and stops firing mid-word\n\nPrivate key blocks are fully redacted and secret rules no longer fire inside longer identifiers.\n\n**What**\n\nThe redactor that masks secrets before they leave your machine now detects PEM private key blocks by scanning for matching BEGIN and END lines with at least 64 characters between them, replacing the whole block with `[REDACTED]`, and loops so several keys in one text are all caught. High-confidence rules now require a non-word character on both sides, so they no longer trigger inside a longer identifier.\n\n**Details**\n\n- The private key detector is added to the rule list as its own rule and reports as \"Private Key\".\n- Candidates that look like a shell fragment or a path\/URL are now left alone instead of being masked.\n\n**Evidence**\n\n`[REDACTED]`, `{ ruleId: \"private-key\", label: \"Private Key\" }`\n\n- Area: Secret Redaction\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}