Earlier quoted context omitted.
I guess that's why they're killing of third party printer drivers as well: https://news.ycombinator.com/item?id=37473628
They're not killing off printer drivers entirely, but they are moving them to userspace. A good idea that should've been implemented a long time ago, in my opinion, though I suspect printer driver manufacturers would've thrown a hissy fit if they actually did so back in the day.
Microsoft plans to kill off NTLM authentication in Windows 11
51–60 of 86 posts
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#52So for the uninitiated, what was the issue with NTLM that makes everyone happy they're switching to kerberos?
I'm a Security Architect dealing with the pain of an old environment with a default NTLM configuration so i'll chime in: - NTLM doesn't sign packets. If you can intercept an NTLM auth request you can forward that authentication attempt to another resource and impersonate the user without needing to know or crack their password. You simply MitM the challenge-response between the client and the server. This is called N…
NTLM provides signing and sealing using a session key. It is the responsibility of the protocol using NTLM for auth to use that key to sign or seal. The problem is that this feature is frequently turned off.
So it's actually not accurate to say "NTLM is vulnerable to relay attacks". If someone turns off signing in SMB to improve performance, that is not a problem with NTLM, that is a problem with the operator turning off signing. If a door has a lock but it's left unlocked, is that a problem with the security of the door?
NTLM also calculates a MIC over all of the NTLMSSP tokens which provides integrity protection independent of the protocol using NTLM. That MIC includes the target SPN so even if signing is turned off, it cannot be hacked.
Regarding hashes, there are two types of NTLM hashes. There are the password equivalent hashes which are only accessible through hacking system memory of a compromised machine that has access to them. It suffices to say, this is not the path of least resistance for an attacker. This is also known as "pass the hash".
Then you have what are called NetNTLMv2 hashes within the NTLMSSP tokens exchanged during authentication. These are muxed from the password and challenge using MD4 and MD5 but also RC4 if key exchange is used (session key mentioned above). This is not trivial to break. It could easily take a room full of GPUs months and maybe never depending on the generator and complexity of the password.
The problem with NTLM is not so much with the NTLM protocol itself but with the various implementations that either don't implement the necessary security features or they simply get turned off. Last I checked Windows Server domain members do not require clients to negotiate signing by default. If an acceptor required an SPN and a MIC, that would stop a relay attack even if signing wasn't used (because they would not be able to forge the MIC without the password and the MIC factors in the SPN).
Another issue is that the security community needs to find issues to justify their existence. NTLM being oldest and relatively weak crytographically naturally draws a lot of critisizm. But the facts are obscured and hyperbolized regularly. People largely regurgitate what they hear without really knowing what they're talking about. They need to to make it at least sound like they know what they're talking about. The only way anyone REALLY knows how this stuff works is to studying the documentation ([MS-NLMP].pdf), looking at captures and step through computations in code.
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#53Is this going to break things like SAMBA?
No. NTLM is an ancient protocol that dates back to Windows NT 3.1 in 1993. That's thirty years ago. Microsoft has been actively telling customers to "please stop using this" for over 10 years. Enough time has passed. NTLM is the Telnet of file sharing. There was a time and place for it and that time has passed.
I have no idea how to set up Kerberos. It looks like I need a Kerberos domain or something? It seems a lot more complicated.
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#54Earlier quoted context omitted.
They're not killing off printer drivers entirely, but they are moving them to userspace. A good idea that should've been implemented a long time ago, in my opinion, though I suspect printer driver manufacturers would've thrown a hissy fit if they actually did so back in the day.
They tried in Windows 8 and printer driver manufacturers did throw a hissy fit. It was one of the big propaganda sources for "UWP is terrible" discourse because UWP gave the best printer experience for userspace printer drivers and that was Windows 8's carrot incentive to try to get the driver writers to upgrade. Rather than accept the carrot most of the driver writers jumped straight into "UWP is bad and no one want…
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#55Earlier quoted context omitted.
Samba has supported Kerberos for a while. I'm sure there's some IoT shit that will break with NTLM disabled, but I believe maintained servers shouldn't be impacted.
Doesn't Samba only support Kerberos as part of a full Active Directory deployment? Switching to Kerberos authentication is not just a matter of flipping a switch, it drastically raises the minimum required infrastructure.
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#56Earlier quoted context omitted.
I'm wondering more about Workgroup networking. I can understand dumping it for domain controllers, but what authentication is used on domain-less networks?
It's in the article: (and the whole reason for finally killing off NTLM) > However, Microsoft is now working on two new Kerberos features: IAKerb (Initial and Pass Through Authentication Using Kerberos) and Local KDC (Local Key Distribution Center). > "The local KDC for Kerberos is built on top of the local machine's Security Account Manager so remote authentication of local user accounts can be done using Kerberos,"…
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#57Is this going to break things like SAMBA?
No. NTLM is an ancient protocol that dates back to Windows NT 3.1 in 1993. That's thirty years ago. Microsoft has been actively telling customers to "please stop using this" for over 10 years. Enough time has passed. NTLM is the Telnet of file sharing. There was a time and place for it and that time has passed.
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#58Earlier quoted context omitted.
To be fair, finding a good printer is hard. Mid-range enterprise printers manufactured before 2006 are in great demand, because of the progress of enshittification by the industry.
Or you can buy a Brother and spend your time on anything else. Let markets do their thing!
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#59How will file and printer sharing work with computers that are only in a workgroup and not a domain?
Re: Microsoft plans to kill off NTLM authentication in Windows 11
#60Earlier quoted context omitted.
Doesn't Samba only support Kerberos as part of a full Active Directory deployment? Switching to Kerberos authentication is not just a matter of flipping a switch, it drastically raises the minimum required infrastructure.
That's definitely the most common way to deploy Samba with Kerberos, but I don't think it's strictly necessary: https://blog.dan.drown.org/kerberos-for-windows-without-ad/