Short version: GPLv3 is specifially desinged to be anti-company, and you are going to see a ever widening schism in the FSS/OSS community between GPL and all the other licenses, and you will be seeing less and less GPL code in commercial OSes and more BSD/Apache/&c code.' Part of locking down OS X security profile required removing anythign that used GPLv3. A few seconds of thought will reveal why Apple is unwilling to provide copies of the keys they use to sign system software. 'GPLv3 makes it impossible to provide signed binaries without also providing the signing keys. So Apple does not supply Samba server in 10.7 and later, because Apple can't just ignore the GPLv3 licensing terms for current versions of Samba - they are the required terms of use as put in place by. That incompatibility was fixed in a version of Samba that Apple *cannot* use, due to the adoption of GPLv3 for current versions of Samba. Lest anyone think otherwise, the prior (now extremely old) versions of Samba that Apple had been using (up tot but not after Mac OS X 10.6) do not provide support for domain-style accounts for Vista nor - especially - Windows 7- so nothing beyond basic file-sharing, ie: no domain-style profiles hosted on the server. Strings /usr/sbin/smbd | grep smbx | wc -lĮxcerpt of strings /usr/sbin/smbd | grep smbx PROJECT:smbx-136.18 In 10.7 and 10.8, mount_smbfs is still provided but that is also not invoked when making a clientĪs far as 'Samba' server goes in 10.7 and later, /usr/bin/smbd is actually Apple's 'smbx'. There is a smbclient binary supplied in 10.5 and 10.6 but that is not invoked when making a clientĬonnection (to a Samba or CIFS (Microsoft server) sharepoint via the Mac OS X Finder.

I've seen a number of uninformed and misguided posts about 'Samba' in Mac OS X 10.7 and later, in various locations online, and most recently here in the Spiceworks 'Apple Group' area.Īs of 10.7 and later, Apple no longer provides Samba server.Īs far back as 10.5, Mac OS X does *NOT* use Samba for client connections

Smbd on mac