> For the complete documentation index, see [llms.txt](https://alham-rizvi.gitbook.io/alhamrizvi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alham-rizvi.gitbook.io/alhamrizvi/cryptography/basics/04.bruteforce-attacks.md). # 04.Bruteforce-Attacks ### What is a Brute Force Attack? A brute force attack is a method where an attacker tries **all possible combinations** of passwords or keys until the correct one is found. Simple idea: **Try everything until something works** *** ### When is it Used? * When no other easier vulnerability is found * When passwords or keys are **weak or short** * In CTF challenges (very common) * When attacker has access to login or encrypted data *** ### Why Does it Work? * Computers can try **millions of guesses per second** * Humans often use **weak passwords** * Small key size means fewer combinations If enough time is given, brute force can break anything in theory. *** ### Simple Example Password = `123` Possible attempts: ``` 000 001 002 ... 123 (found) ``` *** ### Types of Brute Force * **Simple Brute Force** → Try all combinations * **Dictionary Attack** → Try common passwords * **Hybrid Attack** → Words + numbers (example: admin123) *** ### Common Tools * **Hydra** Fast tool for brute forcing login services like SSH, FTP, HTTP * **John the Ripper** Used to crack hashed passwords * **Hashcat** Very fast password cracking using GPU * **Burp Suite** Used for web-based brute force attacks using Intruder *** ### Real-World Use * Password cracking * Penetration testing * CTF challenges * Breaking weak encryption *** ### How to Prevent It * Use **strong passwords** (long and complex) * Enable **rate limiting** * Use **CAPTCHA** * Enable **2FA (Two-Factor Authentication)** *** ### One-Line Summary **Brute Force = trying every possible key or password until success** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://alham-rizvi.gitbook.io/alhamrizvi/cryptography/basics/04.bruteforce-attacks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.