3 ms·

Aaah.. SAMBA :D I read the samba hacker guide and how they had reverse-engineered the protocols over the years. MS Windows is not even compatible with ITSELF f

• jra_samba 7y ago
  That was then but this is now :-). Microsoft now employ Samba Team members, fully document all the protocols used by Windows and help other vendors implement them. This is not your father's Microsoft :-).
  • rini17 7y ago
    I'll bite. How is it then possible that Windows10/Samba interop is more problematic as in my father's times? Unless there was a domain, it worked pretty much out of the box before. Now: https://serverfault.com/search?q=samba+windows+10 https://serverfault.com/search?q=samba+windows+10
    • jra_samba 7y ago
      It certainly isn't more problematic. You should see the volume of complaints we used to get :-). A lot of the issues are usually around authentication and user mapping. Kerberos is complex, and Unix people don't understand Active Directory. That's usually the core of it. Once you get a connection things mostly just work (except for Windows ACLs, for which I blame the Linux kernel developers who refuse to add Andreas Grunbachers RichACL patch set for ideological reasons). Sadly enough, if you want ACLs to "just work" on Linux you have to use a license-incompatible ZFS backend for which Samba has native ACL support. Or just use ZFS-on-FreeBSD where the license isn't a problem. It's one Linux filesystem developer in particular who is blocking the RichACL patch, who is known to be,... shall we say... "difficult" ?
      • amaccuish 7y ago
        Samba stores the ACLS in xattrs right? So they only problem is that they're not applied locally on the host?