08-31-2022, 06:07 PM
hashcat doesnt have an option to output generated hashes to file
this reminds me of the "good old days" and pregenerated rainbowtables, take a look at https://freerainbowtables.com/ and see how big these files are or how big they can be, there are some reasons why rainbowtables are considered "obsolete" nowadays
rainbowtables dont work on hashes which are salted and/or have a different or even a random iteration-count as you have to store all possible iterations for one pass (im asking myself right now: is there a hashalgo out there with random iterationcount but not storing it to the generated hash, so you have to go to all possible iterations to check the pass??? good question...)
okay back to topic, there is no option and given your example with bitcoin wallet, you would store 100000 hashes (each 305 bytes) so ~ 30 megabyte for your passwords with a salt and an iteration-count you will never ever be confronted with again, as each new wallet will use another random salt and another random iteration count, so you will just waste storage
if you want to speedup things when attacking again this hash and you dont want to retest already tested passwords, take a look at hashcat the brain functionality
this reminds me of the "good old days" and pregenerated rainbowtables, take a look at https://freerainbowtables.com/ and see how big these files are or how big they can be, there are some reasons why rainbowtables are considered "obsolete" nowadays
rainbowtables dont work on hashes which are salted and/or have a different or even a random iteration-count as you have to store all possible iterations for one pass (im asking myself right now: is there a hashalgo out there with random iterationcount but not storing it to the generated hash, so you have to go to all possible iterations to check the pass??? good question...)
okay back to topic, there is no option and given your example with bitcoin wallet, you would store 100000 hashes (each 305 bytes) so ~ 30 megabyte for your passwords with a salt and an iteration-count you will never ever be confronted with again, as each new wallet will use another random salt and another random iteration count, so you will just waste storage
if you want to speedup things when attacking again this hash and you dont want to retest already tested passwords, take a look at hashcat the brain functionality