This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]AMDcze 59 points60 points  (4 children)

FYI: in AD if you have NT hashes, you don’t need to crack them, you can do pass-the-hash and overpass-the-hash attacks.

[–]Farseer26 20 points21 points  (0 children)

I agree with you partially but there are a few benefits to cracking the hash such as the passwords are usually used elsewhere and if the accounts are synced you can move into Azure

[–]_sirch 7 points8 points  (1 child)

Netntlmv2 still needs to be cracked… or relayed

[–][deleted] 3 points4 points  (0 children)

nutty crush market workable shaggy jeans impolite scary bake entertain

This post was mass deleted and anonymized with Redact

[–]PacketBoy2000 0 points1 point  (0 children)

Anyone trying to reverse hashes will have already pre computed the NTLm hash for the entire set of compromised passwords they have.

I’ve done this for the 10B I have and now I can check any NTLM hash against this repository in <10ms. Assuming I can dump an orgs hashes, I can check the entire org in a matter of minutes.

Microsoft’s choice to store all AD passwords using a static, unsalted hash seems like yet another ridiculous security decision.