4 ms·
This is mostly an issue in active directory networks. Usually the reason people give as to why they still have this enabled is due to some legacy system that ca
by mr_mitm 9mo ago
This is mostly an issue in active directory networks. Usually the reason people give as to why they still have this enabled is due to some legacy system that can't authenticate via Kerberos or at least NetNTLMv2. Worst case is if they then enable NetNTLMv1 on the domain controllers, even if the DC acts as a client. Using authentication coercion, this is a pretty quick win for an adversary.
- tialaramex 9mo agoOk, so it's a 2 on my list. Microsoft needs to make this forcibly change the UI so that users can see "Oh! I'm using crap low security Windows". That lights a fire under people to actually get it fixed.
- rainonmoon 9mo agoUsing any variant of NTLM is insecure, which is why Microsoft is phasing it out in Windows 11/Server 2025. Which means we should be free of it some time around 2060.