crack2.py freezing on method 2
Posted: Tue Jan 24, 2017 7:40 pm
I've tried several versions of crack2.py from the Ask an Expert forum, and each version is hitting the same point and not proceeding: Using method 2 and searching with 6 password wheels. I'm using Python 3.6.0, running it from IDLE, and I've tried it on 2 different machines:
1. Win10, Intel i7-4770K [email protected], 32GB Ram, 500GB SSD C: drive and a 4TB data drive.
2. Win10, Intel i7-3520M [email protected], 16GB Ram, 100GB SSD C: drive and a 128GB USB 3.0 drive
I've gotten the same issue with all the variants we've tried, but the version we would like to modify to our needs is from Re: crack2.py Not working viewtopic.php?f=30&t=14151&hilit=passwo ... =15#p50088. We're aiming to test the time to process 8-character passwords of varying complexity. That version supports running a list of (at least?) 6 passwords with one keystroke.
We've tried to troubleshoot it, but we can't figure out how (num_pass_wheels) is determined. It seems to be "searching with 6 password wheels." no matter how long the password is. Not sure if that is causing it locking it up, but we'd like to figure out where it comes from before we start tinkering with the program.
Thanks for any assistance.
Gary
1. Win10, Intel i7-4770K [email protected], 32GB Ram, 500GB SSD C: drive and a 4TB data drive.
2. Win10, Intel i7-3520M [email protected], 16GB Ram, 100GB SSD C: drive and a 128GB USB 3.0 drive
I've gotten the same issue with all the variants we've tried, but the version we would like to modify to our needs is from Re: crack2.py Not working viewtopic.php?f=30&t=14151&hilit=passwo ... =15#p50088. We're aiming to test the time to process 8-character passwords of varying complexity. That version supports running a list of (at least?) 6 passwords with one keystroke.
We've tried to troubleshoot it, but we can't figure out how (num_pass_wheels) is determined. It seems to be "searching with 6 password wheels." no matter how long the password is. Not sure if that is causing it locking it up, but we'd like to figure out where it comes from before we start tinkering with the program.
Thanks for any assistance.
Gary