simplify regex for secretPrefix, secretSuffix #1620
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This pull request should not change any functionality, it only simplifies the regex generated by GenerateSemiGenericRegex and GenerateUniqueTokenRegex a bit, in order to make them easier to understand, (and to make gitleaks.toml 4 KB smaller :-)
based on the sidenote in #1467
Changes:
I am not quite certain whether
"|"
was intended to be included in the character ranges, or whether the intention was that[a|b]
should match only a or b, like[ab]
.But since the previous regex for identifierSuffix and secretSuffix match for
"|"
, this patch does not change that.I removed \r\n from the secretSuffix, since it is already included in \s
I also replaced
\x60
with `As far as I could tell, the backtick does not need to be escaped in a toml file, and it was only slightly inconvenient to escape it in code:
However, I may have misunderstood the ramifications, and can of course undo that if desired.
I have also written some unit tests covering GenerateSemiGenericRegex and GenerateUniqueTokenRegex, in a separate pull request #1623
Checklist: