2 ms·
It’s an old, old protocol full of 90s crypto mistakes - passwords could be brute-forced in hours over a decade ago, it still uses things like MD-5, etc. and the
by acdha 3y ago
It’s an old, old protocol full of 90s crypto mistakes - passwords could be brute-forced in hours over a decade ago, it still uses things like MD-5, etc. and there are attacks which cannot be solved within that protocol such as “pass the hash” where you can obtain a hash from a compromised system and use it to authenticate elsewhere even though you don’t have the original password.
There’s a long history here:
https://en.wikipedia.org/wiki/NTLM https://en.wikipedia.org/wiki/NTLM
The main problem is that there’s no way to reliably patch old stuff. If you have a large network, leaving NTLM enabled means attackers will continue to exploit it but as long as it’s an option slacker enterprise IT departments and vendors will continue to delay replacing it. Microsoft deprecated the protocol more than a decade ago so now they’re forcing the slackers to actually do it.
- cryptonector 3y ago> It’s an old, old protocol full of 90s crypto mistakes ... To be fair the same can be said for Kerberos. It's just that Kerberos has kept up with the times more.
- canucker2016 3y agothe weak hashes part is by design - US government design. Exporting software with strong crypto wasn't possible before the late 1990s. see https://en.wikipedia.org/wiki/Export_of_cryptography_from_the_United_States https://en.wikipedia.org/wiki/Export_of_cryptography_from_th...