We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I know it's a lot to ask but it would be great to have GPUs from different clients working on one job.
I know that the skip and limit parameters can be used to split up cracking jobs but finding the right split points will be tough. Two ideas would be:
Both solutions would only work if the key space is deterministic , with makes working on larger maskfiles or rulesets + wordlists very complicated.
Also the splitting up of chunks is highly dependent on the hashtype (10 min MD5 vs 10 min Keepass)
The text was updated successfully, but these errors were encountered:
👍
Sorry, something went wrong.
No branches or pull requests
Hi,
I know it's a lot to ask but it would be great to have GPUs from different clients working on one job.
I know that the skip and limit parameters can be used to split up cracking jobs but finding the right split points will be tough. Two ideas would be:
Both solutions would only work if the key space is deterministic , with makes working on larger maskfiles or rulesets + wordlists very complicated.
Also the splitting up of chunks is highly dependent on the hashtype (10 min MD5 vs 10 min Keepass)
The text was updated successfully, but these errors were encountered: