-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed challenge for eap 11:22:33:44:55:66:77:88 #30
Comments
for example , this service do netntlmv1 for free if the chal is set to this |
I second this. Being able to set a fixed challenge would be incredible helpful with DES cracking, since then only 1 exhaustive search would be needed to find the keys for any number of captured handshakes using the same challenge. |
Any update about this? |
The MsCHAPv2 specification is different from NetNTLMv1, although similar. The main difference is that the challenge is computed as follows: ChallengeHash = SHA1(PeerChallenge + AuthenticatorChallenge + Username)[:7] where So it is unfortunately not possible to set the |
Hi
Would it be possible to set a fixed challenge for eap to 11:22:33:44:55:66:77:88 ?
I believe it would help to crack the netntlmv1 .
Thanks
The text was updated successfully, but these errors were encountered: