[Bugfix] Updated AudD API Token Detector #4233
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
The AudD API token detector was using the
setCallbackUrlendpoint for token verification which is unoptimal for that purpose. As suggested by AudD, the verification endpoint has been changed togetStreams.Any API requests with the
User-Agentheader containingTruffleHoghave been disabled by AudD until a more suitable endpoint is used for verification.Indeterminate verification has also been added to the detector.
NOTE: This PR has been set as a draft until the detector can be tested with the
User-Agentheader containingTruffleHog.Checklist:
make test-community)?make lintthis requires golangci-lint)?