Language Selection

English French German Italian Portuguese Spanish

Microsoft’s Got Nothin’ – The Patent “War” Against Linux

Filed under
Linux
Microsoft
Legal

In the last three years, Microsoft claims to have entered into over 600 licensing agreements with companies small and large over alleged patent violations in "Linux". One consistent feature of all these agreements is that their contents are unknown. No one, other than Microsoft and the relevant "licensee", knows which parts of "Linux" violate which patents. Another consistent feature is that most of the "licensees" are small companies without the resources to take on Microsoft in a patent claim. However, there are a number of larger or more high profile companies that have also entered into such agreements, including Amazon, Novell, Xandros, Turbolinux, TomTom and most recently HTC. The whole situation is clouded in mystery under a veil of PR speak and mumbo jumbo. So what the hell is going on? What can we deduce from what we know so far?

The Who

The identity of the companies that have entered into these arrangements is an important factor to consider. Most of the companies involved are small, and presumably have small, or non-existent patent portfolios; basically companies vulnerable to attack by a company with the financial power, and massive patent portfolio, of Microsoft. These are companies that, when faced with a patent claim by Microsoft, will happily enter into a "friendly" licensing agreement, rather than risk death by a thousand patent wielding lawyers.

rest here




More in Tux Machines

Linux Gaming For Older/Lower-End Graphics Cards In 2018

A request came in this week to look at how low-end and older graphics cards are performing with current generation Linux games on OpenGL and Vulkan. With ten older/lower-end NVIDIA GeForce and AMD Radeon graphics cards, here is a look at their performance with a variety of native Linux games atop Ubuntu using the latest Radeon and NVIDIA drivers. Read more Also: Wine 3.0 open-source compatibility layer now available

Red Hat Patch Warning

  • We Didn't Pull CPU Microcode Update to Pass the Buck
  • Red Hat Will Revert Spectre Patches After Receiving Reports of Boot Issues
    Red Hat is releasing updates that are reverting previous patches for the Spectre vulnerability (Variant 2, aka CVE-2017-5715) after customers complained that some systems were failing to boot. "Red Hat is no longer providing microcode to address Spectre, variant 2, due to instabilities introduced that are causing customer systems to not boot," the company said yesterday. "The latest microcode_ctl and linux-firmware packages are reverting these unstable microprocessor firmware changes to versions that were known to be stable and well tested, released prior to the Spectre/Meltdown embargo lift date on Jan 3rd," Red Had added.

Android Leftovers

Security: Updates, SOS Fund, IR, ME, and WPA

  • Security updates for Friday
  • Seeking SOS Fund Projects
    I’m spending some time over the next few days looking for the next round of projects which might benefit from an SOS Fund security audit.
  • Strong Incident Response Starts with Careful Preparation
    Through working every day with organizations’ incident response (IR) teams, I am confronted with the entire spectrum of operational maturity. However, even in the companies with robust IR functions, the rapidly evolving threat landscape, constantly changing best practices, and surplus of available tools make it easy to overlook important steps during planning. As a result, by the time an incident occurs, it’s too late to improve their foundational procedures.
  • The Intel Management Engine: an attack on computer users' freedom
    Over time, Intel imposed the Management Engine on all Intel computers, removed the ability for computer users and manufacturers to disable it, and extended its control over the computer to nearly 100%. It even has access to the main computer's memory.
  • What Is WPA3, and When Will I Get It On My Wi-Fi?
    WPA2 is a security standard that governs what happens when you connect to a closed Wi-Fi network using a password. WPA2 defines the protocol a router and Wi-Fi client devices use to perform the “handshake” that allows them to securely connect and how they communicate. Unlike the original WPA standard, WPA2 requires implementation of strong AES encryption that is much more difficult to crack. This encryption ensures that a Wi-Fi access point (like a router) and a Wi-Fi client (like a laptop or phone) can communicate wirelessly without their traffic being snooped on.