-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
timeout issues #3215
Comments
Related to #3201 |
Tracing things for the PrivateKey detector, I think I've determined that the server I'm using on my network won't allow me to do this:
It sits there for 15 minutes, and then:
|
Should be resolved now by #3161 |
Re-opened. It seems that #3161 didn't fully address this and was in the release that you reported. |
also see an issue with JDBC:
|
Are these the two targets for testing PublicKey? I would need to make sure that the server that I'm testing from has access to those server:port locations? github.com:22 Are there any other targets? I'm assuming the JDBC test would need to be able to reach whatever JDBC connection is targeting. |
Yes those are the two targets for now. You are correct about database verification. |
Working on getting a fix in for the privatekey detector here |
Please review the Community Note before submitting
TruffleHog Version
trufflehog 3.81.8
Trace Output
and then it just sits there for 15 minutes...
and then continues and finishes up:
Expected Behavior
Adhere to the 10 second timeout.
Actual Behavior
the detector doesn't timeout for 15 minutes.
Steps to Reproduce
trufflehog --trace git https://dev.azure.com/asdf/zxcv/_git/qwerty -j --fail --only-verified
Environment
RHEL 8
Additional Context
Doesn't happen on every repo I scan, but it happens on many of them. I'm guessing any that have a match on the "PrivateKey" detector.
References
The text was updated successfully, but these errors were encountered: