14-11-2016: Currently looking something like in the picture. Over 70 million inserts on new database. Only about 14 000 000 000+ inserts to go.
09-11-2016: All previous hashes even if result "Not Found!" are going to go to new run with 1,5 billion hash database after finished.
07-11-2016: I'm going to add more space to my server and start constructing 1,5 billion hash table.
06-11-2016: Got script working and none of users input was found from my 65 million md5 and sha1 database. I tested it with one of the hashes in the database and it returned correct response in about 0.015 seconds. I think I have to improve it by brute force tools.

Hash Cracker guide and how it works

  • When you go to Hash Cracker you see following field as in the picture but nothing at the result field because you have not send anything to the queue yet.
  • You must type in HASH and NOT PLAIN TEXT. Hash Crackers idea is to crack hashes. Hash -> Back to plain text.
  • You must select type from right corner (MD5, SHA1..) so my server known what kind of hash type it is working with (how ever this could be done programmatically).
  • When you send hash to job queue it's going to be checked by php script that length matches given type. Otherwise job will not be added at all.
  • Finally you see your job at Result's box.
  • Note: if you delete whole application -> new UUID will be generated, meaning that you will not see your later job's again.
  • When job is ready, this is what you will see. Result is green and plain text is shown.
  • If cracker did not find match for your hash, result will throw error text saying "No match found"
  • Click result hash to copy it on clipboard.
  • Long press result to set it as received, which will delete it.
  • Click right corner servers image to see server's statuses. Servers which are responsible for the tasks.
This is what happens after you post job to queue
  • DB/APIs server get's your job and inserts it to database.
  • Cracker servers are polling new tasks from DB/APIs server all the time. When new job is found, cracker server uses word lists to find matching hash that user has given. What ever happens if cracker founds match or not, it's then sends result back to DB/APIs server ready for users output.
Server's like these ones will be responsible for tasks like this. This is an old refurbished HP DL360 G4 (last image) which has been sitting without a work couple of years. It's time to give it a final go with project like this. I have similar refurbished but older generation server also for this feature (DL380 G3). Time will tell is this system going to work. I have some old slow switches that should be used till they die completely and this is good use for them.

If you are interested where I got these old servers, look for Bargain Hardware (http://www.bargainhardware.co.uk/) but when I bought them, this company had only ebay page. Much newer generation server available these days.