The Microsoft settlement
[Posted November 6, 2002 by corbet]
Tempting as it may be to pass over the final judgement in the Microsoft
case as not being of interest to Linux users, the truth of the matter is
that there are a couple of things worth saying. Even though this
settlement looks an awful lot like "business as usual."
Free software advocates had hoped, for a while, that the settlement would
at least require the opening of formats and protocols. Imagine the great
things the Samba team could do if it had to spend less time reverse
engineering everything. In the end, the final settlement offers nothing of
value in this regard. Consider:
- Microsoft is required to license its protocols under RAND
terms. These terms involve license fees, of course, and are thus
quite discriminatory against free software.
- Microsoft does not have to license to companies which have a
"history of software counterfeiting or piracy or willful
violation of intellectual property rights." Potential
licensees also have to convince Microsoft of the "authenticity and
viability" of their business, and submit their code to Microsoft for
verification.
The most interesting provision with regard to licensing, though, may well
be this one:
No provision of this Final Judgment shall... Require Microsoft to
document, disclose or license to third parties: (a) portions of
APIs or Documentation or portions or layers of Communications
Protocols the disclosure of which would compromise the security of
a particular installation or group of installations of anti-piracy,
anti-virus, software licensing, digital rights management,
encryption or authentication systems, including without limitation,
keys, authorization tokens or enforcement criteria; or (b) any API,
interface or other information related to any Microsoft product if
lawfully directed not to do so by a governmental agency of
competent jurisdiction.
As has been pointed out by others, the "security" argument could be used to
lock up just about anything that Microsoft does not want to release. And
why, exactly, does the U.S. government reserve to itself the right to
suppress the release of API and protocol information? One assumes that
somebody has something in mind here.
After five years, the entire settlement goes away.
The bottom line is that this decree is not going to help the free software
community to any great extent. But, then, it never really was going to.
Attacking Microsoft is not a useful goal for the free software community;
our purpose is to create and distribute the best free software we can.
And, for those who wish to
see Microsoft in discomfort, it is worth noting that free software has
already caused the company much worry. Microsoft's planned takeover of the
server space has been thwarted, and the company's grip on other computing
markets, while still firm, just does not look as invulnerable as it once
did. Editors, compilers, and the free software development process may yet
prove to be the most effective weapon against software monopolies.
(See also: yet
another leaked Microsoft memo, duly marked up by Eric Raymond. This
one is a survey of opinions toward Linux. "Closing, those who are
familiar with OSS and Linux are favorably predisposed towards them. Linking
this work with other on-point research, we can assume that in the majority
of cases this reported 'favorability' is more emotional than it is
rational.")
(
Log in to post comments)