-
Notifications
You must be signed in to change notification settings - Fork 125
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
Setting a value for jitter has no effect #35
Comments
Hi @lag! The jitter (as of now) does not effect the sleep between each attempt, however it does effect sleep between each 20 accounts attempted. And since this is done async, console log wise it might look the same as without. I will correct this feature in an coming update so it does infact sleep between each login attempt! |
I absolutely love your tool @Flangvik - I was previously jumping through hoops to use other tools with some of your core features like shuffle regions, usernames etc. It would be awesome though if the Jitter worked per user attempt, as sometimes the tenants are very small, sub 50 users and all the attempts close together seem to get gripped by the lockout even with a long sleep window. Thanks again for creating such a great tool :) |
Thanks for the kind words of encouragement @DannHacks, i'll see what i can do about this |
Hey @Flangvik, thanks for the fast reply, that would be great! If that value could be changed to randomise per login attempt, that would be even sweeter 😋 Again loving the tool dude! ❤️ |
Hi.
I was testing the program with the following command:
./TeamFiltration --config TeamFiltrationConfig_Example.json --outpath testclient --spray --debug --jitter 10 --passwords passwords_for_testing.txt --shuffle-users --shuffle-passwords
Spraying otherwise works fine, but changing the jitter value has no effect on the functionality. TeamFiltration will just spray as the jitter was 0. I tried hardcoding the value to 60 with no effect, maybe there is an issue with the Thread.sleep in Spray.cs on line 180?
The text was updated successfully, but these errors were encountered: