07-26-2018, 08:12 AM
(This post was last modified: 07-26-2018, 08:18 AM by cesalbaral.)
(07-26-2018, 07:37 AM)philsmd Wrote: $HEX[2474406d66307264210d40313233] means that hashcat is trying to use the string 2474406d66307264210d40313233 in hexadecimal notation (it's in hexadecimal because there are some non-printable or "escaped" characters, like colons etc).
2474406d66307264210d40313233 stands for $t@mf0rd!\r@123
427279616e6164616d73313131390d40313233 stands for Bryanadams1119\r@123
as said, these strings are represented in hexadecimal instead of ascii/utf8 because they contain some special characters (in your case the carriage return character \r). You can use a hex to ascii/utf8 converted to analyze the password candidates.
I would guess this has to to with your rules and/or dict file. If you do not want to use these special characters like carriage return you need to modify your dicts/rules.
My guess is that everything works as intended it's just a misunderstanding
Thanks, I found that the problem was with the wordlist. The wordlist was craeted on windows using a python script called cupp. Converting it into UNIX Worldlist through this terminal command solved the problem:
Code:
tr -d '\015' <windows.txt >UNIX.txt
But I still don't know if it's necessary to do this or not.
Is hashcat using the displayed hex codes or is it using those words on the list to perform attack?
Anyway my problem has been solved for right now.
Also are you sure that you coverted those hexadecimal scripts correctly. That /r wasn't supposed to be in the password.