Add logic related to 'max' flag #34
Merged
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
hahwul
approved these changes
May 21, 2024
There was a problem hiding this comment.
Hi @isacaya
I apologize for the delay in reviewing your pull request. Thank you so much for your contribution and your patience. Your PR looks great, and I'll merge it shortly.
Test
./jwt-hack crack {TOKEN} --max 2 -m brute
./jwt-hack crack {TOKEN} --max 5 -m brute
./jwt-hack crack {TOKEN} --max 10 -m brute
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.
Added logic to use the max flag, since the max flag was not used in bruteforce.