SecLists VS naive-hashcat

https://github.com/danielmiessler/SecLists/blob/master/Usernames/xato-net-10-million-usernames.txt is not enough usernames

This reminds me of [0] where they maintain composite lists of frequently used passwords. Also in the repo is probably my favorite pull request ever [1].

[0] https://github.com/danielmiessler/SecLists

[1] https://github.com/danielmiessler/SecLists/pull/155

Maybe swagger.txt

Typical of the sorts of information a tester/attacker might be using from: Daniel Miessler's SecLists

Oh, and then you have this.

You can now also enable a rule for password dictionary. Appwrite knows what are the most common passwords, and with this rule enabled, it will not allow you users to set any of those passwords. It prevents your users from having passwords like password, 123456678, or qwertyui. Appwrite currently knows the 10,000 most commonly used passwords thanks to the same list used by other industry-leading auth providers. You can check out the dictionary list on GitHub.

Try wifite if you don’t know how to use hashcat it is pretty simple. Hashcat is pretty easy as well I am to lazy to get on my laptop right now but just get the right wordlist Seclist has a shit load of them https://github.com/danielmiessler/SecLists

Fellow rust players know the way

For this, I downloaded wordlists such as the rockyou wordlist and used tools such as Hashcat and John the ripper.

For decrypting the .cap file, we've different techniques. We'll use simple technique using aircrack-ng only. It'll help us crack the password using a wordlist. You can use rockyou.txt wordlist which is most commonly used & is updated on regular basis.

First, any sort of password that uses an actual word (English or otherwise) has a far greater chance of being cracked. This is due to the fact that common password lists (e.g. the rockyou list) contain millions of unique entries from sites around the web. Many people share a favorite animal or plant as well, so unless your favorite animal is something unique like Mustela erminea there's a good chance that it's an entry in a list somewhere.

Most of the time a DB of hashed passwords is leaked/stolen and the attacker has unlimited attempts to brute force that. What's also commonly done is that they run it against dictionaries (and there are some pretty good dictionaries for that and some of them are easily accessible online) and if the DB is large enough, they're practically guaranteed to get hits immediately.

Looking at the GitHub page for naive hashcat, it appears as though it only takes at most three arguments. Is there a reason you're using it over regular hashcat?

First, it is important to know how the process works. Hashing is a process essentially different from encryption - you can only do it once. It means that we cannot really recover the plaintext of a hashed password; instead, we can only compare its hash with our guesses. So, it's like hashing several words and seeing which of them matches exaclty our hash. Then, it must be the password. We can automatize this process with two tools: hashcat and a dictionary of potential passwords. This kind of dictionary is easy to find on internet, so we are going to use rock you.

I use only SecLists (https://github.com/brannondorsey/naive-hashcat/releases/download/data/rockyou.txt)

rainbow table ("dictionary") plaintext or broken list of common passwords (i.e. Rockyou) leaked from many sources ^ those give you an idea of what people think are "clever" passwords

It's important to choose strong passwords. That's because there are lists of millions passwords like rockyou.txt which can be used to brute force your Linux system using hydra.