7 ms·
Apple replaces Samba for Windows networking services
- __david__ 16y agoI'm confused, which part of the GPL v3 makes it impossible for Apple to distribute?
- equark 16y agoWell they can't link it against anything proprietary. Presumably they want to link into Finder in some way or into some of their other filesystem APIs.
- pedrocr 16y agoThat can't be the case as GPLv2 has the same requirements in that area and Apple seems to be perfectly happy with it.
- js2 16y agoSee http://lists.samba.org/archive/samba/2010-October/159151.html http://lists.samba.org/archive/samba/2010-October/159151.htm... for some discussion
- thaumaturgy 16y agoI don't see how anybody could read the GPL FAQ (http://www.gnu.org/licenses/gpl-faq.html http://www.gnu.org/licenses/gpl-faq.html) and not come away confused. It's awkward as hell. And then there's this part: > I'd like to incorporate GPL-covered software in my proprietary system. Can I do this? > You cannot incorporate GPL-covered software in a proprietary system. ...followed by a series of ifs-and-buts that include completely vague terms like "at arms length". MacOS X is a proprietary system. It includes support for Windows file sharing. Assuming that Samba was used for this, does this mean that MacOS was not incorporating Samba? Or does it mean that Apple was in violation? Or does it mean that somehow Apple was meeting one of the vague requirements for separation between Samba and MacOS? (I'm not raising this as a question of differences between GPL v2 and GPL v3.) Given the case histories involving the GPL so far, I could see Apple's legal team advising Apple to put as much distance between them and the GPL as possible. Non-compliance due to one gray area or another could force Apple to release tons of proprietary source code. I think that shrugging this situation off with "well, that's their decision" is completely disingenuous. Yes, it's their decision to make, but they will most certainly decide in a particular way as a direct result of the situation they're looking at.
- kevinpet 16y ago<i>Non-compliance due to one gray area or another could force Apple to release tons of proprietary source code.</i> No, it cannot. Anyone who repeats this FUD is revealing he has no understanding of the issues. The GPL may not be exceedingly clear, but this is entirely an issue of copyright law. Maybe they will be forced to stop distributing something until they replace a component, and maybe they could be forced to pay damages, but there is no mechanism that the GPL could force them to release anything they didn't want to.
- thaumaturgy 16y agohttp://en.wikipedia.org/wiki/BusyBox#GPL_lawsuits http://en.wikipedia.org/wiki/BusyBox#GPL_lawsuits > The case was settled with release of the Monsoon version of the source and payment of an undisclosed amount of money... > The Xterasys case [ed: separate case] was settled on December 17 for release of source code used and an undisclosed payment. (I'm not including cases that were settled with a stipulation of "active compliance".) http://en.wikipedia.org/wiki/GPL#The_GPL_in_court http://en.wikipedia.org/wiki/GPL#The_GPL_in_court > Cisco settled the case six months later agreeing ... to make source code of FSF programs freely available on its website. Granted, that last one doesn't sound all that bad. Given that the GPL does compel the release of source code for derivative works, and given that one of the FSF's tactics in lawsuit settlements is to ask for the release of source code, let's not go misapplying the FUD label, OK? edit: I don't mean that to sound snarky. Rather, I'd like to see less "Bah, that's just FUD", and more explanation and clarity when responding to people's concerns about the GPL.
- tzs 16y agoThose companies settled because they wanted to continue distributing their products as is. Hence, they released source in order to be allowed to do that. They could have instead replaced the GPL code with non-GPL code, possibly paid some damages, and been done with the matter with their source remaining secret.
- caf 16y agoSettlements are agreements. No-one was forced to release source code, which is the language you used. It was their choice - they could have held out if they had wanted to. You can't force a GPL violator to release source. All you can do is offer them a deal where they release the source in exchange for less/no monetary damages.
- pedrocr 16y agoNothing prevents redistribution, v3 seems to be equal to v2 in all the code sharing requirements. The two big-ticket additions seem to be the prevention of "tivoization" by having to distribute the keys to sign software to run on the device you distribute with GPLv3 software in it, and the requirement that if you grant some users a license to one of your patents you're granting that to every user of the GPLv3 software you distribute. One reason Apple would care is it is now shipping a bunch of locked down hardware (the iDevices). Although those probably don't run Samba right now they may have set up a general policy to not have that risk. http://en.wikipedia.org/wiki/GNU_General_Public_License#Version_3 http://en.wikipedia.org/wiki/GNU_General_Public_License#Vers...
- yuhong 16y agoI remember discussing this on a GCC mailing list back in mid-2008.
- tzs 16y agoA bigger problem may be licenses to other people's patents. Suppose Apple distributes Samba, and suppose someone NOT Apple owns a patent that Samba infringers. That party sues Apple, and it becomes clear to Apple that they are going to lose. Let's also assume Apple's Samba has some changes, so it is not 100% identical to the upstream. It looks like GPLv3 only gives Apple the option of stopping distributing Samba, or of finding a way to get a patent license that covers everyone who obtains a copy of Samba that can be traced back to Apple. The latter could get very expensive.
- bcrescimanno 16y agoIANAL, and I don't claim to have any specific knowledge of the GPL v3 vs. v2--however, my guess is that Apple employs at least a decent legal team who has concluded that the changes in GPLv3 may include language that could force them to open source more of OS X than they're comfortable with. Or, it may be completely unrelated to GPLv3 and Apple simply no longer wishes to "walk a fine line" in this particular area.
- deleted 16y ago[deleted]
- gte910h 16y agoIt's not that they'd have to release the source code, it's the cryptographic keys they'd have to release for iPhone stuff, as the code is ALSO on iOS, and you can't change it without the crypto keys. You never have to release source code if you violate the GPL, you just have to stop distributing the item till you rip out the GPL code, and pay damages to the copyright holder for infringement.
- gte910h 16y agoThe part about cryptographic keys. It makes it so code signing on the iOS version of the MacOSX kernel would have to have public keys (the anti-tivoization provisions of GPLv3).
- icarus_drowning 16y agoWon't this be easy to get from MacPorts soon enough anyway?
- bcrescimanno 16y agoThe obvious question is: why would anyone want to? Presumably, Apple will replace Samba with something that works well for the vast majority of cases. To me, this echoes my problems with the GPLv3: how can software be truly free (as in freedom) if it's not free to be used commercially?
- SoftwareMaven 16y agoWhile I agree about the problems with the GPL, freedom is such an overloaded term with different meanings having different levels of importance that it is effectively meaningless.
- tptacek 16y agoIt is free to be used commercially, if you write it, pay for it, or keep its derived works open source. The only thing GPLv3 keeps you from doing is closed-source commercialization against the wishes of the author. This seems eminently reasonable to me. If you want to allow people to do closed-source commercial projects with your code, BSD license it.
- chc 16y agoIt feels kind of like a semantic game to call free software "commercial." Do you really believe that, in general, consumer software that you essentially have to surrender the copyright to is commercially viable? Are many people actually going to pay for something that's available for free with literally no added benefit? (I am, of course, ignoring support here, because support is really a separate product that could even be provided by a third party.)
- oihujyfgthyjuik 16y agoDepend s- is your app commercially viable if you have to re-implement all the GPL stuff I wrote for you yourself? If you are using my GPL contributions for free then you can't turn around and stop your customers using those contributions.
- 38leinad 16y agoi have lately been writing a simple "samba" client for iOS (https://github.com/38leinaD/tango https://github.com/38leinaD/tango) and after that experience i must say to the developer doing the samba replacement at apple: poor bastard; you are in for a world of pain! It is really a horrible protocol where you can see how it evolved and was extended from windows version to version...
- ch0wn 16y agoSetting up a working file server with basic authentication is almost enough to confirm this. There might be valid reasons for all of the configuration options, but the avarage user will never need more than 10% of them.
- ajl2011 16y agoumm unsigned int data_length = *((unsigned short *)(parameters_ptr + parameters_offset)); parameters_offset+=2; .... memcpy(buffer_ptr, ((unsigned char *)(smb->data_ptr + payload_data_offset)), data_length); you should probably fix a few things :> in your case it's probably not that bad.. I for one can't wait to see what security holes apple will bundle with new releases osx
- wmf 16y agoSolaris also replaced Samba with in-house code: http://blogs.sun.com/amw/entry/cifs_in_solaris http://blogs.sun.com/amw/entry/cifs_in_solaris IIRC this is a lot easier than it used to be now that MS has to publish protocol specs.
- henrymazza 16y agoGood point! In your link: > "[Samba] is a portable, user space application, and is actively supported on Solaris. [on the other hand] The Solaris CIFS service is a native kernel implementation; a first-class citizen of the Solaris operating system"
- calloc 16y agoI used it within OpenSolaris and the real pain is that you have to set up entirely new NFS ACL's that relate to the user writing otherwise files won't be readable from within Solaris as that user, or if it is a shared directory they aren't readable by the outside world and the files are written to disk but no longer visible from the outside world over the network.
- radiowave 16y agoYes. In general any time you want to access the same file system by multiple different methods, the permissions issue gets rather hairy, but from the point of view of an Apple CIFS server, some well considered finesse in the GUI could be a big help in managing that complexity. In the case of OpenSolaris, it's at least worth mentioning that so long as you do only want to treat a file system as being a share for CIFS clients, it does work just beautifully.
- codex 16y agoApple's filesystems already support native NTFS ACLs, so I expect that the permissions issues will be no worse than current NTFS/POSIX interop, which is indeed hairy. The best you can do is support the POSIX case very well and the all-ACL case very well.
- thwarted 16y agoIf they can make it work and well integrated, that would be great. The Samba integration on OSX Server is, IMHO, extremely subpar. I had problems with file permissions and ownership getting set correctly. And that's just for fileserving, which samba has had downpat for years, not things like having it be a DC in a AD setup. I know what the options are to have samba do what I want, but there is no place in the lowest-common-denominator-of-file-sharing-service-configuration GUI to set them. And you really want to avoid hand editing the GUI maintained configuration files because they get overwritten.
- lukeschlather 16y ago"Extremely subpar" may be overly charitable from my experience. We had constant problems that have pretty much disappeared since we replaced it with a machine running Windows Server 2008 R2. My biggest gripe was discovering that for a user foo, you can't just give the user permission to access a file on a network share through the GUI, you must also make sure that foo can access the file at the Unix level. Potentially I guess if they're building from the ground up they can get better integration, though I'm skeptical of their ability to do better than Samba.
- thwarted 16y ago"Extremely subpar" may be overly charitable from my experience. I like to say that anyone who thinks all Apple products are designed well and work as you expect means that person has never used OSX Server. My biggest gripe was discovering that for a user foo, you can't just give the user permission to access a file on a network share through the GUI, you must also make sure that foo can access the file at the Unix level. In some sense, this is the way samba works (it uses file system permissions for user share mode, once they've been authenticated, unless you override it with things like the force user, force group, or force mode parameters -- which you can't effectively set on OSX). Unfortunately, since the GUI hides actual samba configuration from you, you never find this out.
- robin_bb 16y agoI consider this to be a failure of a GPL-licensed open source software project. Samba is not being used by Solaris, nor by Mac OS X.
- wmf 16y agoDevelopers who use the GPL don't want as many users as possible; they want freedom and users can take it or leave it.
- JoeAltmaier 16y ago...and they have mostly left it in this case. Fine; but lets not pretend open-source GPL projects are significant to the world at large; they are backroom projects with no future.
- jscott1290 16y agoare you kidding me? gcc?
- JoeAltmaier 16y agoI use gcc. Its a constant struggle compared to commercial, supported compilers.
- tjarratt 16y agoUpvoted, as I agree with you philosophically, that the GPL is not exactly a corporate developer's best friend. However, neither Solaris nor Apple are typical corporations in terms of using licensed 3rd party code; given the terms the GPL poses, wouldn't you expect to see more smaller companies, or companies that operate primarily on the web to adopt GPL'd projects?
- dave1010uk 16y agoWill Samba loose out from this? Are Apple an active developer of Samba?
- deleted 16y ago[deleted]
- codex 16y agoTo this I say, "good riddance." Samba is a pretty horrible implementation of a pretty horrible protocol. It was originally built by systems administrators, so I'd say that the system is more "accreted" (like a stalactite) rather than really designed. Samba is incredibly hard to extend and maintain and the primary developers are more wankerish and ideologically motivated than commercial vendors would like. Primarily for these reasons, but also for licensing reasons, EMC, NetApp, other storage vendors, Oracle, and now Apple have all switched over to private implementations. I believe Sun's effort started long before protocol documentation was available from Microsoft, but the Samba developers do deserve credit for doing some incredibly painful reverse engineering, even if that reverse engineering is sometimes incomplete.
- Stormbringer 16y agoThat's an interesting perspective. I had been under the impression that the concept/implementation was fine, until Microsoft started diddling with the system in order to mess them around. Specifically: wasn't Samba based on a 'clean room' implementation of some Microsoft protocol or something like that? And when it took off Microsoft were in the middle of their 'kill Linux in the enterprise at all costs' jihad and so they kept changing the protocol that the Samba guys were trying to interface/interact with?
- codex 16y agoIn a word, no. Microsoft could not change the protocol because it still had to support the hundreds of millions of Microsoft Windows clients out in the field. With Vista, Microsoft cleaned up the protocol a bit (SMB2), but it was the Samba team's paranoid fantasy that this somehow applied to them. Really, it was a long-overdue revision which helped performance tremendously. While the Samba team had a huge task, this does not excuse the extremely crappy implementation over the years: corrupt TDBs, lack of change notify, no native ACL support, oplock crashes due to the non-asynchronous, single threaded nature of each smbd, horrible Winbind scalability problems, domain join bugs, no real named pipe abstraction layer, no alternate data stream support, etc. And the code is just horrible to look at.
- Stormbringer 16y agoThe GPL has done a lot of good, but I think it is rather hobbled by being tied so intimately to the concept of 'linking', which has a very clear technical meaning when talking about C/C++, but becomes a lot fuzzier when applied to other languages. This was fine back when all software was written in C/C++... except that was of course never the case.
- viraptor 16y agoWhat are the chances that the new service is actually samba-tng (http://wiki.samba-tng.org/doku.php/start http://wiki.samba-tng.org/doku.php/start) ? That would be at least interesting. Otherwise - good luck to them replicating what samba project learned over the last 20 years. A new implementation has slim chances of being compatible with systems in the wild.