Private-key redaction no longer stalls on large or malformed input.
What's wrong with this entry?
The secret scanner that strips private keys out of text before it leaves the session no longer uses one large regex spanning the whole key block, which could stall on big or malformed input. It now finds BEGIN and END lines separately and splices out what lies between them.
- Two case-insensitive global patterns, one for the header and one for the footer, matched in sequence with a minimum 64-character gap between them.
- Each matched region is replaced with
[REDACTED].
PRIVATE KEY(?: BLOCK)?-----
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.
-
v2.1.232
GitLab token detection grows from 2 patterns to 11
Both mention secret redaction
-
v2.1.232
GitLab tokens are now stripped from logs and error output
Both mention secret redaction
-
v2.1.232
Nine more GitLab token types are caught by the secret scanner
Both mention secret redaction