How does bruteforcing passwords work?
Wouldn't you need to send a request to the application server to check the result for each attempt to crack the password, and wouldn't this take a very long time?
i.e., how do bruteforce attacks attempt so many combinations in such a short amount of time and verify if the combination is correct without hitting the server millions of times?
Usually you already have the hash if you are considering brute force as a viable option.
>>60336415
>How does bruteforcing passwords work?
basically you run the ever loving fuck out of your computer's CPU and it generates billions of guesses and eventually you get it. Although remember every EXTRA character your password contains takes an exponentially longer time to crack
26 letters + 26 capitals + 10 numbers + a large number of special characters means every character extra multiplies by something ridiculous every time
>>60336415
You steal the database first you idiot. Google sqt. You're clogging up /g/ with retarded threads.
>>60336518
Google first or post in sqt*
>>60336415
Don't most password programs now have a limit on how many tries you can attempt?
Brute forcing on modern systems is obsolete. That's why key loggers were created.
>>60336582
see
>>60336443
>>60336518
Now stop bumping this thread.
>>60336582
There are bypasses to this