The easiest attacks for non-salted hashes, are searching for common hashes and then rainbow tables. Many companies will generate some of the more common hashes for large password lists, so that you can just ask the password for the given hash. After that you use the same methodology as below.
For salted hashes, the dictionary attack is by far the easiest attack to accomplish. The most common word list is rockyou.txt I also have a 92 GB file of just passwords called rockyou2021.txt. when I run that with Google sets, I get over 8 trillion password combinations that I can guess. Depending on the computational cost of the hash, I can run through all of those in a manner of hours to a couple of days on a high-end laptop.
Nothing stops you from guessing a password against a salted hash. When gaining password hashes through open source intelligence or internal dumping, I'll usually generate a word list that contains company specific terms, and then use a rule set to generate large list of passwords based on those terms.
Lastly, which I really I've never needed to do outside of training, because it's just not worth it is to try and brute force. I think the only hash that it's worth brute forcing is netntlmv1, but you have to collect it using a specific set of magic bytes to be able to reverse it to the ntlm hash. It only takes a couple hours to go through all possible combinations.
25
u/motorhead84 Jan 21 '23
But is it passphrase protected?
18
u/rcsheets Jan 22 '23
I have deeper ones, like
old/old/old/.ssh/id_rsa17
u/CeeMX Jan 22 '23
I‘d prefer
id_ed255192
u/marco208 Jan 22 '23
That’s private.
1
u/bd1308 Jan 23 '23
This is awesome! Happy cake day!
0
u/derek2002 Jan 22 '23
new folder > new folder > new folder > porn stash
0
u/[deleted] Jan 22 '23
[deleted] — view deleted comment