+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html)
+--- Forum: General Help (https://hashcat.net/forum/forum-8.html)
+--- Thread: hash issues (/thread-4355.html)
hash issues - pulsar1279 - 05-12-2015
Hi all,
Having issues getting cudahashcat to love me, an approximation of my hash is below, along with the corresponding error message.
the hash is from the first : (colon), to the next one, the $1$ I would think is -m 500, but l've also tried 20, 1500 or anything else I can think of.. It's a slax root pwd on a penetration practice disk..
Any help/advise appreciated greatly...
this is root.hash..
$1$xxxxxxxx$j3obHaAlUdMbHxxxxY5Dq0
cudahashcat64 -m 500 -a0 root.hash /root/dict/rock410.txt -o recovered.txt
cudaHashcat v1.31 starting...
WARNING: Hash 'root.hash': Signature unmatched
ERROR: No hashes loaded
RE: hash issues - radix - 05-12-2015
cudahashcat64 -m 500 root.hash /root/dict/rock410.txt -o recovered.txt
RE: hash issues - pulsar1279 - 05-12-2015
Still gives me signature unmatched - no hashes loaded
RE: hash issues - pulsar1279 - 05-12-2015
and I haven't got any leading or trailing spaces...
RE: hash issues - pulsar1279 - 05-12-2015
Ran the same through hashcat rather than cudahashcat64... and it worked... what would be the difference?? have run cudahashcat64 on wpa passwords with success, any ideas anyone? thanks
RE: hash issues - philsmd - 05-12-2015
You need to specify the correct path to the file "root.hash".
On linux for instance you can use tab-completion or use "ls" to check if the file really exists at the location you think it exists.
For instance this:
WARNING: Hash 'root.hash': Signature unmatched
... means:
"I was unable to find the file 'root.hash' within the current working directory, I did try to parse the parameter 'root.hash' as a hash directly, but this didn't work either because the string 'root.hash' is not a valid md5crypt hash"
In other words oclHashcat/cudaHashcat whenever it fails to find the hash file specified on command line, it tries to parse the command line as hash directly (while hashcat cpu does not).
Solution: fix the path to the hash file (best for testing is to use absolute paths, e.g starting with /... , but relative paths work too if you know the exact (relative) position)
RE: hash issues - pulsar1279 - 05-12-2015
Thanks I'll give it a go..
RE: hash issues - pulsar1279 - 05-12-2015
I think that's solved... awesome, thanks philsmd.. much appreciated, nice to be able to use the gpu..