Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entropy trace #1659

Merged
merged 4 commits into from
Dec 30, 2024
Merged

Entropy trace #1659

merged 4 commits into from
Dec 30, 2024

Conversation

almaz045
Copy link
Contributor

@almaz045 almaz045 commented Nov 26, 2024

Description:

Explain the purpose of the PR.

Checklist:

almaz045 and others added 2 commits November 25, 2024 15:49
… trace

Maybe I'm wrong, but it seems to me that if the regex allowlist is large, it's easier to first check for entropy, since we won't have to go through all these regexes. Plus, we need to check entropy anyway.
Additionally, when using -l trace, there was no information that the find was missed precisely because of entropy. Now it will be shown
@zricethezav
Copy link
Collaborator

@almaz045 do you mind resolving the conflicts here? then I'll get it merged

@almaz045
Copy link
Contributor Author

@almaz045 do you mind resolving the conflicts here? then I'll get it merged

done

@zricethezav zricethezav merged commit b69b515 into gitleaks:master Dec 30, 2024
1 check passed
@rgmz rgmz mentioned this pull request Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants