cracking password with part of it knowm - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: cracking password with part of it knowm (/thread-7430.html) |
cracking password with part of it knowm - mike1982 - 04-08-2018 I need to crack a series of hashed passwords and for some reason, it's exhausted without cracking the password. The passwords are given to me in the form of NCL-HQNT-XXXX, with the last 4 being numerical digits. I've been doing a lot of reading up on this and it should be straight forward. My command is: hashcat -m 0 -a 3 crackthese NCL-HQNT-?d?d?d?d --force The hashed passwords are in the "crackthese" file (5 of them). Also, this is for NCL, but not the competition. I'm still working in gymnasium. Just FYI, so you know I'm not trying to cheat on this. I'm still trying to learn it. Any idea what I'm doing wrong? Thanks RE: cracking password with part of it knowm - DanielG - 04-09-2018 Big question is why are you using "--force", maybe it has to do with the error you are suppressing. What is your entire output when not using "--force"? RE: cracking password with part of it knowm - mike1982 - 04-13-2018 (04-09-2018, 08:52 AM)DanielG Wrote: Big question is why are you using "--force", maybe it has to do with the error you are suppressing. What is your entire output when not using "--force"? It won't run at all when I don't use force. Output: + Device #1: Not a native Intel OpenCL runtime. Expect massive speed loss. You can use --force to override, but do not report related errors. No devices found left. Update on issue though. It actually ran and cracked if I omit -m 0 from the command. I guess it autodetects that it was MD5. However, I run into a similar situation when trying to crack SHA256 passwords. I believe it's -m 1400. When I omit the command for this one, it says line-length exception. RE: cracking password with part of it knowm - mike1982 - 04-13-2018 shoot. nvm. That time it was a typo in the static part of the password. Thanks |