3 ms·
Microsoft made exactly the same mistake years ago with SMB. Once the 3rd-party open-source client, Samba, was written, it emerged that SMB access restrictions
by w0mbat 6y ago
Microsoft made exactly the same mistake years ago with SMB.
Once the 3rd-party open-source client, Samba, was written, it emerged that SMB access restrictions were only in the Microsoft SMB client software not the SMB server.
Samba users could do whatever they wanted.
- tupputuppu 6y agoIs there a source for this? Can't find anything with a quick googling?
- w0mbat 6y agoYou know, this happened so long ago, in 1992, that there may be nothing for Google to find. I mean the web had been invented, but there wasn't much of it at that point. SMB server was updated eventually, so that it checked user access rights and didn't rely on the client not to request a file it wasn't allowed to see. SMB1 however continued to be horribly insecure, sending passwords in plain text, for example, which led to SMB2, SMB3 etc.