3 ms·

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 st

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.

jeroenhd 3y ago
Microsoft has said the same about SMB2 but people still turn that back on because of old NASes and printers. Most guides for Samba still seem to be written with NTLM in mind. Any Linux/*BSD based consumer NAS may break, as well as many hobbyist NAS setups. Microsoft is right to get rid of these old, vulnerable protocols, but there may still be an impact.
- wannacboatmovie 3y ago
  If NAS builders can't cope with this change maybe they shouldn't be in the NAS business.
  - jeroenhd 3y ago
    Many of them probably shouldn't, but if customers buy a new computer and their old workflow doesn't work on the new one, they're going to blame and "fix" the new computer rather than replace additional hardware.
- IntelMiner 3y ago
  Isn't SMB2 meant to be the "mostly good" one introduced in Vista? SMBv1 was an absolute shit-show. A lot of early devices only supported it using hacked up ancient GPL violating Samba builds
  - jeroenhd 3y ago
    SMBv2 is better but still not great. SMBv3 is pretty good. SMBv1 is a security risk that should've been deleted from the Windows source code long ago.
SirMaster 3y ago
I looked up my Debian file server and apparently it's using NTLM between it and my Windows desktop to share files. 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.
TheNewsIsHere 3y ago
I get the sentiment, but I think a batter example is needed. Telnet is still very useful for troubleshooting purposes.
cryptonector 3y ago
Kerberos and PKI go back just as far (further). The thing is that NTLM has never been fixed up to keep up with the state of cryptography.

jeroenhd 3y ago

Microsoft has said the same about SMB2 but people still turn that back on because of old NASes and printers. Most guides for Samba still seem to be written with NTLM in mind. Any Linux/*BSD based consumer NAS may break, as well as many hobbyist NAS setups. Microsoft is right to get rid of these old, vulnerable protocols, but there may still be an impact.

wannacboatmovie 3y ago
If NAS builders can't cope with this change maybe they shouldn't be in the NAS business.
- jeroenhd 3y ago
  Many of them probably shouldn't, but if customers buy a new computer and their old workflow doesn't work on the new one, they're going to blame and "fix" the new computer rather than replace additional hardware.
IntelMiner 3y ago
Isn't SMB2 meant to be the "mostly good" one introduced in Vista? SMBv1 was an absolute shit-show. A lot of early devices only supported it using hacked up ancient GPL violating Samba builds
- jeroenhd 3y ago
  SMBv2 is better but still not great. SMBv3 is pretty good. SMBv1 is a security risk that should've been deleted from the Windows source code long ago.

SirMaster 3y ago

I looked up my Debian file server and apparently it's using NTLM between it and my Windows desktop to share files. 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.

TheNewsIsHere 3y ago

I get the sentiment, but I think a batter example is needed. Telnet is still very useful for troubleshooting purposes.

cryptonector 3y ago

Kerberos and PKI go back just as far (further). The thing is that NTLM has never been fixed up to keep up with the state of cryptography.