Language Selection

English French German Italian Portuguese Spanish

Is Microsoft really any more trustworthy?

Filed under
Microsoft

Lately, Microsoft has been trying really, really hard to appear as open source’s best friend. All I can say is: “With friends like these, who needs enemies?”

Microsoft has been making all these wonderful promises of opening up APIs and protocols. The company just forgot to mention that it is only obeying the orders of the European Union court system.

If someone stole from you, and the courts ordered them to pay you back, how would you feel about them holding a self-serving press conference to tell you how generous they are? Or, as Michael Tiemann, head of the Open Source Initiative and a Red Hat executive, put it in an OSI blog posting on March 30th, Microsoft’s new weapon against open source: stupidity.

You see some people still believe that Microsoft offering patented protocols under “reasonable and non-discriminatory terms,” or “for free for noncommercial use without fear of lawsuits” is somehow some kind of olive branch to the open-source community.

More Here

Also from SJVN:

I couldn't make it to OSCON last week in Portland, OR, but I have read the announcements that Sam Ramji, the director of Microsoft's Open Source Software Lab, made at this open-source software show. They were the friendliest things I've ever seen come out of Microsoft towards open source.

The first announcement, that Microsoft was contributing a patch to ADOdb, a PHP database access interface, wasn't that big a deal. It is, after all, self-serving. Microsoft's contribution will enable people to use its own SQL Server instead of MySQL or PostgreSQL with PHP programs. Yawn. Nothing new here.

The second announcement, that Microsoft was placing its Communications Protocol Program under its Open Specification Promise, and clarified that developer could use the communication protocols to build open-source software for commercial use, sounded much more important than it really is. You see the European Union courts ordered Microsoft to open those protocols up. Samba and the SFLC (Software Freedom Law Center) hammered out an agreement late last year that spelled out how the protocols could be used while avoiding Microsoft patents.

Could Microsoft actually be getting an open-source clue?




More in Tux Machines

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.

First Impressions: Asus Tinkerboard and Docker

The board's standard OS is TinkerOS - a Linux variant of Debian 9. I've also read that Android is available but that doesn't interest us here. While Android may use forms of containerisation under the hood it doesn't mix with Docker containers. Rather than trying TinkerOS I flashed Armbian's release of Ubuntu 16.04.03. The stable build on the download page contains a full desktop, but if you want to run the board headless (like I do) then you can find a smaller image on the "other downloads" link. I initially used the stable image but had to swap to the nightly build due to a missing kernel module for Kubernetes networking. Having looked this up on Google I found the nightly build contained the fix to turn on the missing module. Read more

today's howtos