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

Remove the custom generic Gitleaks rule as it's not needed anymore #472

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

spaze
Copy link
Owner

@spaze spaze commented Jan 16, 2025

It was added in #76 to detect "dev" and "prod" keys, but I've since started to use prefixed encryption keys in #269 so the custom rule is not needed anymore. This is why you use prefixed keys, it makes things simple, and I like making things simple.

Also, the custom generic rule started throwing many false positives after I've upgraded to Gitleaks 8.23.1 for some reason.

It was added in #76 to detect "dev" and "prod" keys, but I've since started to use prefixed encryption keys in #269 so the custom rule is not needed anymore. This is why you use prefixed keys, it makes things simple, and I like making things simple.

Also, the custom generic rule started throwing many false positives after I've upgraded to Gitleaks 8.23.1 for some reason.
@spaze spaze self-assigned this Jan 16, 2025
@spaze spaze merged commit 41b377e into main Jan 16, 2025
37 checks passed
@spaze spaze deleted the spaze/gitleaks-update-rules branch January 16, 2025 03:11
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.

1 participant