Slashdot Mirror
Microsoft Tech Specs Prohibit GPL Implementations
abartlet writes "As described in this Advogato entry, MS is trying to pull a swifty with their latest 'release' of their CIFS (the networked filesystem Samba implements) Technical Reference. The licence specifically prohibits any GPLed or (or LGPLed) program from implementing it, defining it as an 'IPR Impairing Licence'! Fortunately the CIFS community is about to release its own Technical Reference based on earlier MS documents and long experience in attempting to interoperate with the MS product." Microsoft's claim is completely ungrounded - nothing written by a third-party can take away Microsoft's intellectual property rights. But it makes a good (read: confusing to the general public) justification for preventing others from interoperating with their software.
Go to the linked MSDN doc, and "Rate this Page". We can at least register our disgust that way.... (It's already at 1.3 out of 5, 1 being the lowest possible :-)
It is well known that one of the places that Window's succeeds in is small/middle sized network configurations. You plug in hardware, install (costly) software, and everything nearly automagically works. Files are shared. Printers are shared. With a little domain administration you can even tightly control it.
The fact that the Samba Team has created such a successful implementation of the same smb/cifs kills this completely. Note the "(costly)" part in my previous paragraph goes away if you use Samba instead of a WinNT Server. And no goofy licenses either(how many seats do I need to buy?). And now that Samba has set their sights on implementing recent features like Active Directory why wouldn't Microsoft be running scared? Take away this feature from Windows and you've undercut their monopoly on administration software of Windows networks.
It's an antimatter version of the GPL, like a GPL from the parallel Star Trek universe where everyone was evil.
Microsoft has gone ballistic. It has begun.
Kodak saying no one else can make a set of chemicals that develop their film if they plan to give them away for free?
This is like Kodak giving someone the recipe for the official Kodak set of chemicals, then telling them that they can't give that recipe to other people.
Microsoft is well within their rights under Copyright law here. Microsoft is giving people the opportunity to implement the CIFS specs, but not to redistribute them in a form which makes sublicensing compulsory.
The hole in the situation is that someone could implement the spec and release it to the Public Domain, since MS isn't forbidding ALL redistribution, only direct redistribution with compulsory sublicensing. That code could then be folded into a GPL'd product by a third party since they received the original code as PD, not under Microsoft's agreement.
NO CARRIER
Usually you have to accept the license, because nothing else gives you right to use or copy the software.
Umm, nothing except USC 17, Chapter 1, Section 117
Their license covers the documentation, NOT the protocol itself. Clearly they can't license something that exists only in abstract (here, let me license you some air). If you want to implement SMB, you have two choices--
1) Download the CIFS documentation from Microsoft at the URL provided, and agree to the terms of the license.
2) Reverse engineer (through packet sniffing, etc) the protocol, never touching/reading any of Microsoft's documentation (eg: figure it out on your own).
The section of the DMCA you cited prevents software makers from limiting a customer from reverse engineering a product for compatibility purposes; Microsoft can claim all day long that you can't reverse engineer their OS (and I'm sure they include packet sniffing in their 'reverse engineer' definition), but the law says you have a right to circumvent any measures they put in place to stop you, and (in parts not quoted by the parent) even PUBLISH your results amongst peers.
All I know about Bush is I had a good job when Clinton was president.
Don't be silly.
:-).
This spec is a *subset* of what Samba already implements.
The SNIA CIFS spec (which we helped to create) already
documents far more than is in this spec. (Not that I've
read it this spec, obviously, but I've spoken to people
who have read both).
This spec. is an irrelevence. Try implementing it to
the letter and see how many Microsoft clients actually
*work* against you. (Hint - none
Jeremy Allison,
Samba Team.
This comment is plain ridiculous (not +2 insightful) !
There is nothing in this spec that Samba has not already
implemented.
This spec is irrelevent to Samba.
As to the "will have to switch to a BSD license in order
to add features to Samba".... words fail me !
If you want new features (such as a recycle bin or the
new NT-ACL code) then just keep doing a CVS update from
samba.org. Next release will be 2.2.4.
Regards,
Jeremy Allison,
Samba Team.