-
Notifications
You must be signed in to change notification settings - Fork 211
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
[BUG]: Agent running hashcat command twice #1065
Comments
Hello @ZerkerEOD, a couple of things on what you showed :
From what I can see, everything works as intended in what you showed, and if you wanna make sure, simply run the same commande as called by Another way to check would be through the agent log itself, it should display its current speed on stdout / its default log, depending on your setup, allowing you to confirm the agent sees the same cracking speed, and the check through my previous suggestion that the slowdown is expected, and due to the combination of wordlist and rules instead of BF. |
Thanks for explaining that. Is there a reason that the agent doesn't run hashtopolis on it's own rather than spawning a process to spawn the process? |
Version Information
Hashtopolis: 0.14.2 commit d397e4b
Hashcat
6.2.6+813
Description
When running from Debian, it appears that the agent is starting two hashcat jobs reducing performance speed by over half with some overhead.
Benchmark run from the same binary hashtopolis placed on the box without hashtopolis running:
Here is a ps aux for hashcat with hashtopolis running (note it is running with a
/bin/sh -c
and just a./hashcat.bin
:Here is the reported speed in hashtopolis:
The text was updated successfully, but these errors were encountered: