pagodo (passive google dork) plugin #413
Open
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
Author
|
@1N3 did you had the chance to review my PR? |
|
LGTM |
abnerrizzi
approved these changes
Aug 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added a new plugin called pagodo (PAssive GOogle DOrk).
This plugin starts execution in the background when the osint scan is enabled. It searches for google dork information regarding the target and gathers URLs returned from dorking. Since this scan can take up to many hours it executes in the background without halting the rest execution of Sn1per, it keeps running in the background even after Sn1per has finished executing.
Added two more settings for configuring pagodo, one for enabling the scan and one for using proxy-chains or custom proxy servers for spoofing your IP.