Microsoft Office lock-in and the deal with Novell
I can't urge you strongly enough to read the article entitled How Vista Lets Microsoft Lock Users In. It details how Microsoft has built into Vista the "trusted computing" ability to lock down Office files via DRM such that no unauthorized document reader will be able to decrypt and read them. This is perhaps one of the biggest hidden weapons Microsoft has in its arsenal that could sabotage Linux and OpenOffice.org if Microsoft succeeds in its attempt to plug SUSE and all Novell's "interoperability" bonuses.
Think of this, if you will, as the Tivoization of Office files, only with malicious intent. Microsoft could, indeed, open up the document format completely and swear before God that it will never sue anyone for patent infringement. However, this does not prevent Microsoft from locking Office files in such a way that only Vista users can read them. No one else will be able to do so without the proper authorization, thus rendering the open format and Microsoft compatibility entirely meaningless -- unless, of course, someone agrees to pay Microsoft for the keys to unlock those files.
The lesson here should be obvious. The FOSS community must avoid - at all costs - the practice of adopting or integrating anything into FOSS that is owned or generated by Microsoft. Ximian, and now Novell, has made it a mission to recreate Microsoft technologies on Linux. I urge the community only to allow Novell to continue to do this at its own peril. It was a massive strategic blunder to attempt to recreate dotNet on Linux as Mono. Microsoft has implicitly, by attempting to make patent deals, acknowledged Linux as a genuine threat. That makes it so much greater a danger to adopt Microsoft practices, whether it involves integration of Office document formats, Excel VBA compatibility, or anything else.
This is an ironic twist, to say the least, after all the fuss Microsoft made over the viral nature of the GPL. Microsoft, through Novell, is attempting to infect open source with hooks it can use to profit from the success of Linux at the expense of Linux users' freedoms.
Our message to Novell should be to live free or die.
I want to thank Phil Hughes for bringing the above article to my attention.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Three More Lessons
- Django Models and Migrations
- August 2015 Issue of Linux Journal: Programming
- Hacking a Safe with Bash
- The Controversy Behind Canonical's Intellectual Property Policy
- Secure Server Deployments in Hostile Territory, Part II
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- General Relativity in Python
- Embed Linux in Monitoring and Control Systems