-
Notifications
You must be signed in to change notification settings - Fork 18
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
repository plugin - support scanning historical git commits #66
Comments
for simplicity, suggesting to scan the historical commits for the current checked out branch |
Just saying we are half-based on Gitleaks. Gitleaks is scanning Git history and finds secrets, but our code is based on Gitleaks only for the secrets themselves. Here, your suggestion is just taking the git traversal mechanism from Gitleaks, because we can't take the whole process, we must pass the content into our secrets finder, to support secrets that doesn't exists in Gitleaks. |
@jossef, @bryantschuck, @cx-monicac, @joaopedrocsilva I want to consult with you. Using Gitleaks to search the history of the repository, gives me the following results:
We can say that a specific fragment can be defined by My question is, how should we define an I think, from the user's perspective, he didn't care about the fragment. He only needs to know where the secret was first introduced, so we need to give him the The WDYT? |
@bryantschuck Another question: Do we need to keep support scanning the current existing files in a directory, or we can replace it with scanning all the git history (which finally scans the whole content of the directory + historical changes that were removed over time)? I think we should move the current implementation of "git" as a regular directory to another plugin for scanning the filesystem and not related to Git features. |
- refactor: repository plugin initialization - change repository to filesystem - repository plugin - support scanning historical git commits Fixes #66
repository.go is quite straight-forward implementation.
suggesting to use Gitleaks engine to scan historical commits if they contain secrets
The text was updated successfully, but these errors were encountered: