-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
--since-commit stopped working in v3.67.4 #2396
Comments
@ltbringer https://github.com/trufflesecurity/trufflehog/releases/tag/v3.67.5 just released a new version a minute ago |
Just tested with 3.67.5 -- the issue seems to persist. I can provide a trace, if that's helpful, but comparing it to 3.67.3 I don't see anything useful, except that it never reaches this:
|
I faced a different issue when testing: logs:
|
Would anyone happen to have an example I can work with? Testing this locally I am currently unable to reproduce the broken behavior. If anyone has a publicly accessible repo, or a test setup it would be greatly appreciated. Thanks. |
@ahrav, I've set up a demo of the issue here https://github.com/kpocius/trufflehog/pull/4 |
hey @kpocius I can't thank you enough for taking the time and effort to put together that test setup, i really appreciate it. I've requested a review on the PR attached to this issue. Once that gets merged in i'll cut a release which I believe should fix the issue. Thanks again, and I apologize for lengthy wait to get this fix out. |
Lengthy wait? This is probably one of the fastest turnarounds I've seen 🙂 So if there's anyone we should be thanking, it's you! Happy to help. |
@ahrav, works like a charm! Thank you. |
TruffleHog Version
3.67.4
Trace Output
N/A
Expected Behavior
Only scan branch commits since base.
Actual Behavior
Scan continues across all history.
Steps to Reproduce
Run the following on a branch of the repo which has some pre-existing secrets in history:
Environment
N/A
Additional Context
N/A
References
It seems that some change was introduced in #2387 where it never reaches base commit and just proceeds scanning entire history.
The text was updated successfully, but these errors were encountered: