Many different improvements with new parameters and an automatic file retrieval script #2
Conversation
This file contains 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.
The original PadBuster behavior has not been changed and all commands that used to work should work as expected. Otherwise many modifications have been made. Some are connected with stability and speed, others with usability, configurability and also automation.
As the example autoBuster.sh script shows PadBuster can now be used as a almost fully automated tool for encoding resource paths, bruteforcing and retrieving files from vulnerable server. The user just needs to specify the correct URLs and block size, but he also can run intermediate commands by himself or try out differently configured operation modes.