-
Notifications
You must be signed in to change notification settings - Fork 377
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
Divide by zero error when calculating delay #21
Comments
Started a new spray and added -Delay 1860. I still recieved both the null array and the "ConvertLargeIntegerToInt64" error. It got to the point of "Are you sure you want to perform a password spray..." prompt. I hit yes and it displayed the "1 of XXXX users tested" and froze there. In other words, the "1" did not increment. After a minute I ctrl+c'ed that run, backed out the delay, and started again. Everything seemed to run fine. |
Tagging @egypt Edit: Fixed this by adding Edit2: Inserting my own delay still seems to make it freeze on "1 of XXX users tested" Edit3: Ok, the delay thing might have been my own misunderstanding. My assumption was that this was a customizable delay between each password spray. It looks like it's a delay between each individual account tested though. |
Potential fix for dafthack#21
I am running into this as well. Basically defaults to no wait between sprays. I tried adding
|
As a note here, I didn't set a -Delay value, because it previously defaulted to 30 minutes, which was acceptable. It looks like that default is still there, if I'm reading the code correctly. However, when running the script, I received a divide by zero error and no delay. The error message is reproduced below, please let me know if there is any other information I can provide.
I just noticed a "ConvertLargeIntegerToInt64" error prior to this that may be part of the problem. I missed it earlier because I thought it was another "Cannot index into null array" error. I also received a null array error for line 347 (in addition to the two for 538 and 539) when running Get-DomainUserList.
Edit: Updated to contain more information
The text was updated successfully, but these errors were encountered: