Too many collisions with -m 9720

[philsmd]

If you are referring to the initial post https://hashcat.net/forum/thread-3665-po...l#pid20935 you need to know that this thread was opened before devs even thought about implementing the -m 9710 and -m 9720 kernels (this was the testing phase for only -m 9700 - there was no -m 9710 and -m 9720 yet). You can even see this code he posted:

Code:

if ((digest[0] == swap_workaround (0xf2ab1219)) && ((digest[1] & 0xff) == swap_workaround (0xae000000)))

after atom found the "brute force" result:
$oldoffice$1*d6aabb63363188b9b73a88efb9c9152e*afbbb9254764273f8f4fad9a5d82981f*6f09fd2eafc4ade522b5f2bee0eaf66d:$HEX[f2ab1219ae]

This means, in this particular case you shouldn't rely (only) on the very first post (or at least read the full thread), because there are updates (like this one https://hashcat.net/forum/thread-3665-po...l#pid20945 ), where atom explains the progress and introduces -m 9710 and -m 9720.
Of course it is possible to use -m 9700 to run ?b?b?b?b?b, but the general idea is (again, after -m 9710 and -m 9720 were implemented) that you use -m 9710 and -m 9720 if you want to find collisions.

---

And to answer your original question: actually the main idea of this collision finding was to collect/see as many collisions as possible.
But I actually have a clever trick for you (but please promise me to not tell it to anyone , you can use this command, to almost immediately stop after finding the first collision for the hash(es):

Code:

cudaHashcat64.exe -m 9720 --outfile-check-timer 1 --outfile-check-dir out\ -o out\collision.txt m09720.txt -a 3 ?b?b?b?b?b

(make sure that the folder out\ exist before running oclHashcat)
the outfile-check timer will mark the hash as cracked and therefore oclHashcat will stop cracking

Again, this is a hack and normally you would not need to use -m 9720 like this (stop after first found).