You're right, pyrit can now attack but in the past I've seen issues with attack_cowpatty option, so I decided to generate .cow files with pyrit but then leave the cracking to cowpatty. Of corse you may choose different ways to do it.
Cheers!
What purpose does the passthrough function serve on pyrit? I understand that in earlier versions of pyrit you would use it with cowpatty but now that it can attack handshakes by itself why is it still there? Or is it used for something other than that..?![]()
You're right, pyrit can now attack but in the past I've seen issues with attack_cowpatty option, so I decided to generate .cow files with pyrit but then leave the cracking to cowpatty. Of corse you may choose different ways to do it.
Cheers!
You. Are. Doing. It. Wrong.
-Gitsnik
The passthrough option is for not using any disk space. The hash's are computed on the fly with a wordlist and once finished nothing is saved and no disk space is used.
So then whats the difference between using just the attack_passthrough command in pyrit compared to the passthrough command combined with cowpatty?
The difference is that in the aatack_passthrough instance pyrit does the cracking and in the passthrough the hash's are piped to cowpatty which does the cracking. This is a matter of preference. Cowpatty has a little bit better handshake detection but the author of pyrit is working to improve that.