Microsoft Agrees to Release Work Group Protocols
UnknowingFool writes "Groklaw is reporting that the Protocol Freedom Information Foundation (PFIF) has signed an agreement with Microsoft to release their protocols relating to Windows Work Group Server. The Foundation agrees to pay MS $10,000, and the agreement does not cover patents. This agreement apparently was made to somewhat satisfy the EU Commission complaints. With PFIF's objective to aid open source, this agreement means that the Samba Team may finally get the information they need to fully interoperate with Windows AD servers."
Couldn't or wouldn't? When they were under pressure earlier this decade, Microsoft spent a lot of money lobbying/buying off US state and federal governments, creating fake "grass roots" campaign sites and paying for press releases from pro-corporate lobbyist groups such as the cato institute (source1 source2).
Yes it includes all AD protocols.
Jeremy.
Yes they're true. Please help us. See here :
http://samba.org/samba/devel/
for details.
Thanks
Jeremy.
They way it will work is as follows. We'll read the docs and work on creating client-side test cases and embedding them into Samba4 smbtorture. Once that's in place, any competent engineer can create the server-side implementation without having to have access to the actual docs. We need the test cases anyway (remember, untested code is broken code), so this is the way we've been going about doing things anyway. This should just open up new protocols and new protocol areas to implementation by others.
Jeremy.
Totally legal in the United States. In other jurisdictions, the law is not so clear-cut. In Europe, the right to reverse engineer is not sacrosanct. Then again, Europe doesn't (yet) have software patents.
Standard IANAL disclaimers apply, of course, but I've worked for several companies that relied on reverse engineering precisely for the purpose of compatibility with undocumented file formats. In one such company, I was informed by management (after advice from legal counsel) that it was actually legal not only to reverse engineer the file format, but it was even legal to reverse engineer / decompile the code for the application that generated the files in order to see how they were written -- the caveat being, you could only reverse engineer the code to insure compatibility, not to plagiarize it. (Usually you do a clean room reverse engineering process to insure that the people who reverse engineer the code write a clean spec that the people who write your code then use. The people doing the reverse engineering shouldn't be writing code based on that process, to avoid even the appearance of impropriety.) Of course, that particular employer's policy was to not reverse engineer the code of the applications themselves, only the files they wrote, but if we had the resources and we needed to, we could reverse engineer just about anything we wanted.
The legal climate in the U.S. was shaped in part by the outcome of a case where IBM sued Compaq for reverse engineering the BIOS of the IBM PC. Clearly, Compaq prevailed, and the clone PC market was born.
Off-topic for a second. THIS is why I have continued to suffer the 1:19 signal:noise ratio and goatse trolls on Slashdot since 1997. Especially before the dot bomb, every story had someone directly involved with the situation posting somewhere in the comments.
Got a story about VAX? There are fifteen people with decades of experience on the forum. Bruce Perens is always on any story involving him (sometimes to an annoying level...). You had to know that Jeremy would be posting on this story.
Although less than it used to be, Slashdot still has people I can't see anywhere else. Thank you, Slash!
Put identity in the browser.
But I *loved* the goatse trolls :-). It used to be the only reason I /. :-). I miss sig11 and klerk and the rest of that crew.
/. fun, especially as they drove taco *nuts* :-).
:-).
came to read
They made
Anyone remember the Bruce Perens impersonators ?
Jeremy.