Posts: 10
Threads: 3
Joined: Jun 2018
Hello,
I'm trying to implement support for a file format that has barely any header information in the cleartext to check candidate password validity. Is it possible to return all of the valid candidates from the GPU?
It is my first time adding support for a hash format, but it was not difficult, the code is very well structured.
Thank you very much!
Posts: 930
Threads: 4
Joined: Jan 2015
You can use --stdout to see what candidates hashcat will generate.
Code:
$ echo -n hashcat | hashcat --stdout -r ./rules/best64.rule | head
hashcat
tachsah
HASHCAT
Hashcat
hashcat0
hashcat1
hashcat2
hashcat3
hashcat4
hashcat5
~
Posts: 10
Threads: 3
Joined: Jun 2018
Hi Royce,
Sorry, english is not my native language. I've seen this option, but it doesn't do what I want.
Suppose I found in the GPU code that two different passwords, eg 'Hashcat' and 'HashCat' are 'valid'. But I'll actually have to perform additional checks (eg. see the resulting file when these specific passwords are used). Can I get a list of all the collisions?
Posts: 2,301
Threads: 11
Joined: Jul 2010
hashcat supports an option --keep-guessing which should do what you want
Posts: 10
Threads: 3
Joined: Jun 2018
undeath, thank you. Im using this option, but the passwords are not appearing in any file. Does this option also saves the collisions somewhere? Thank both of you for your time.
Posts: 930
Threads: 4
Joined: Jan 2015
Verify your syntax using an existing format. If it works for that, it should work for yours.
~
Posts: 10
Threads: 3
Joined: Jun 2018
Thanks royce! It worked! The potfile now contains all the found collisions!