-
Notifications
You must be signed in to change notification settings - Fork 37
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
test.py SystemError #23
Comments
That error is interesting. I wonder if it's coming from python or hashcat or somewhere else? Thanks for testing! I'll see if I can reproduce. Might take be next week before I can really dig into it though. |
After a quick look I think the benchmark never ends because of this line ChaCh20 is the last hash tested in benchmark mode so the benchmark is actually completing. My guess is in benchmark mode the status never reaches "Cracked" though. So I'll just have to figure out what signal gets sent when hashcat is finished and then exit the infinite loop. Triggering exit on signals is the correct way of cleanly exiting anyway. |
Thanks for having a look. Looking forward to integrating this into a project I'm working on. Cheers |
It totally files to work on hashcat 3.6.0:
If I change the attack mode to 0, I get an even weirder error:
|
Invalid OpenCL is usually a platform issue not pyhashcat. Make sure you init the dependencies as specified in the hashcat build.md instructions first, then run hashcat normally. If hashcat works as usual then it's a pyhashcat issue. Closing. Tracking OP issues in #25 |
Running test.py with
hc.benchmark = False
results in error output below.Running with
hc.benchmark = True
never exits. Stuck with several lines ofincoming seqnr wraps around
. Full output below.Thanks.
The text was updated successfully, but these errors were encountered: