NTLMv1/NLTMv2 Hashes Appear to be Incorrect - Githubissues

Kevin-Robertson / Inveigh

.NET IPv4/IPv6 machine-in-the-middle tool for penetration testers

BSD 3-Clause "New" or "Revised" License

2.44k stars 433 forks source link

NTLMv1/NLTMv2 Hashes Appear to be Incorrect #13

Closed fullmetalcache closed 5 years ago

fullmetalcache commented 5 years ago

I used the latest version of Inveigh (cloned 2018-11-27) and found the following:

The second field of NTLMv1 hashes appear to only have 47 characters instead of 48.
The second field of NTLMv2 hashes appear to only have 31 characters now instead of 32.

I reverted to previous version of Inveigh that I have that is at least six months old and found that NTLMv1 hashes have 48 characters in the second field and NTLMv2 hashes have 32 characters in the second field (https://github.com/fullmetalcache/tools/blob/master/inveigh_stripped.ps1).

fullmetalcache commented 5 years ago

Disregard, it must have been some weird glitch...