Added '-b' option to rotate through usernames #3
Conversation
Added support for a -b or --backwards flag to rotate through usernames per password, which can sometimes help avoid account lockouts.
|
Hi, Thanks for your contribution! Before I can merge this branch I need to better understand your reasons for this code change. What exactly do you mean by "rotate through usernames"? You can already use the -U option to specify a list of usernames to iterate through. |
|
Many enterprise environments have account lockout policies based on a number of failed passwords in a short amount of time for a user. For example, if Bob has 10 failed password attempts in 1 10-second timespan, lock out the account. But some enterprises might say to only lock out the accounts for a very short time, because we don't want to disrupt the user experience... Instead of trying every password in our list for each user, another option is to try every username for each password. Let's say our password list is: Normally we would try all of these in order for the first user, then move on to the next user. As we increase the size of our userlist, we end up increasing the time between trying the same username twice in a row and in many cases, defeating poor lockout policies. Try it out! Hydra has a similar option "-u" but for ciscobruter the "u" option is already taken. |
|
This functionality as I understand it is already present. Specify a password list with -P and a user list with -U and it will try all the passwords for user 1 and then all the passwords for user 2 etc. Is this not what you are describing? |
1 similar comment
|
This functionality as I understand it is already present. Specify a password list with -P and a user list with -U and it will try all the passwords for user 1 and then all the passwords for user 2 etc. Is this not what you are describing? |
|
No, I've had better results by trying all the users with password 1, then all the users with password 2 etc. Here is an example that I think illustrates it: Userlist.txt: Passwordlist.txt: Traditional method: Backwards: With only 4 users, it shouldn't make a difference. But when you have a few thousand users, and a situation where the lockout policy "resets" the failed password count after, say, 20 or 30 seconds, we may be able to avoid getting the accounts locked out. Unfortunately a lot of places have such silly lockout policies. |
|
Ah, now I get it. So your saying right now the script tries every password for user 1 before moving on to user 2? That's not as effective as the method you are describing. I will look into this further. |
Added support for a -b or --backwards flag to rotate through usernames per password, which can sometimes help avoid account lockouts.