Given a SHA512 hash, a salt, and username I am trying to crack the hash using hashcat. Every example I've found used a hashfile as input, is there way to provide salt and hash via commandline without the need to create a hashfile?

Here is an example what I am trying to crack:

Hash: 6ce9a7c73ebf0c04db026fda907210e7367f6d72225f78399a4a3fc9bfd0cce9
Salt: a3424259-9534-486a-bfe9-6a2b39aa70e5
  • 2
    Have you read the manual? hashcat.net/wiki/doku.php?id=hashcat – schroeder Mar 7 '19 at 20:52
  • @schroeder yes. – n00b.exe Mar 7 '19 at 20:58
  • 1
    then there you go? – schroeder Mar 7 '19 at 20:59
  • @schroeder I didn't find what I was looking for otherwise I wouldnt have asked the question. I know that I can specify the mode with -m but how would I provide the username, salt and the hash in the commandline? – n00b.exe Mar 7 '19 at 21:01
  • 1
    We can't know what you have already checked. The use of the term "shadowfile" suggests you only checked out specific tutorials and not the manual. Why do you want to specify the username? – schroeder Mar 7 '19 at 21:03

According to hashcat's wiki, you can paste the hash directly into the command line:

Usage: hashcat [options]... *hash*|hashfile|hccapxfile [dictionary|mask|directory]...

You can also use hash mode 1710 as in: 1710 | sha512($pass.$salt)| Raw Hash, Salted and/or Iterated

Putting it all together, it would be hashcat -m 1410 -a 0 hash:salt --username test_user /usr/share/wordlists/rockyou.txt where the hash contains the password and salt (in that order).

If the hash is salt/pass instead of pass/salt, use 1420 instead.

| improve this answer | |
  • right ... so how do you put that all together on the commandline? – schroeder Mar 7 '19 at 21:11
  • hashcat -a 0 -m 1710 hashhashhash.saltsalt ? – schroeder Mar 7 '19 at 21:12
  • @SomeGuy You only specified the hash tho? Where do you specify the salt? – n00b.exe Mar 7 '19 at 21:15
  • when you see delimiters such as / or . in a hash string, that's the delimiter for the salt and hash. – SomeGuy Mar 7 '19 at 21:17
  • 1
    @RoyceWilliams As mentioned in one of my earlier comments I realized it is SHA256, not SHA512. But thanks for the clarification! – n00b.exe Mar 8 '19 at 1:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.