Skip to content
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

Open
T3KX opened this issue Mar 25, 2019 · 4 comments
Open

Fixed challenge for eap 11:22:33:44:55:66:77:88 #30

T3KX opened this issue Mar 25, 2019 · 4 comments

Comments

@T3KX
Copy link

T3KX commented Mar 25, 2019

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

@T3KX
Copy link
Author

T3KX commented Mar 25, 2019

for example , this service do netntlmv1 for free if the chal is set to this
https://crack.sh/netntlm/

@TomTervoort
Copy link

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.

@Hackndo
Copy link

Hackndo commented Jul 15, 2020

Any update about this?

@Rogdham
Copy link
Contributor

Rogdham commented Nov 21, 2020

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 AuthenticatorChallenge is chosen by the server, but PeerChallenge is chosen by the client (and Username as well of course).

So it is unfortunately not possible to set the ChallengeHash to 11:22:33:44:55:66:77:88.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants