-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
hashcat3: init at 3.10 #20826
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
hashcat3: init at 3.10 #20826
Conversation
|
||
meta = { | ||
description = "Fast password cracker"; | ||
homepage = "http://hashcat.net/hashcat/"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: You don't need quotes around URLs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, fixed.
For someone not in the know, why not just have version 3? |
Version 3 isn't backwards compatible with version 2, so I figured creating a new package would be the safest option. On the other hand, I can't see any downsides of upgrading to version 3, so maybe replacing the version 2 package is a better idea. |
Version 3 is also problematic, because it depends on OpenCL: see #16623 |
@kierdavis Travis reports a hash mismatch |
@Mic92 thanks for digging that up. Looks like it's probably best to keep hashcat2 around until OpenCL on NixOS is more portable. @joachifm looks like hashcat 3.20 has been released in the meantime, and the URL |
Thank you |
Motivation for this change
We already have a 'hashcat', but it's at version 2.x, which is incompatible with hashcat 3.x.
Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)This builds and runs on my machines, but I'm not yet convinced that it's portable. I'd be grateful if a couple other people could test that this package builds and that running
result/bin/hashcat -b
starts the benchmark running on at least one device (CPU, GPU, APU etc).