Language Selection

English French German Italian Portuguese Spanish

M$ proposals open a window

Filed under
Microsoft

THE Free Software Foundation, the keeper of the sacred flame of open-source software untainted by commercial restrictions, evoked a nice image of Microsoft the other day. It compared its nemesis to an unruly child who throws himself to the floor in a tantrum and has to be dragged to his feet by his parents.

Microsoft has spent a lot of the past few years foot-dragging and whining about imaginary dangers when confronted by regulators in the US and Europe that were unhappy at how it wielded its near-monopoly in desktop operating systems.

But small children have a disconcerting habit of coming up with a good reason to stand their ground just when their parents finally lose patience and start shouting (later to feel guilty). So it is with Microsoft and the argument over whether it should be forced to license its software protocols on terms that would encourage competition from open-source organisations.

Microsoft’s underlying position, if not its louder rhetoric about how its trade secrets are under threat, has a kernel of truth. The European Commission would over-reach itself by making Microsoft publish its intellectual property in the manner suggested by the Free Software Foundation. The laudable objective of stimulating competition can be achieved without forcing the company to behave exactly as open-source purists would prefer.

Full Story.

More in Tux Machines

Android Leftovers

Tidelift Backed by Former Red Hat Chairman and CEO Matthew Szulik

  • Open source startup Tidelift snags $15 mln Series A
    Boston-based Tidelift, an open source startup, has secured $15 million in Series A funding. General Catalyst, Foundry Group and former Red Hat Chairman and CEO Matthew Szulik led the round. In conjunction with the funding, Larry Bohn, managing director at General Catalyst, Ryan McIntyre, co-founder and managing director at Foundry Group and Szulik have all joined Tidelift’s board of directors.
  • Tidelift raises $15M to find paying gigs for open-source developers maintaining key projects
    Tidelift wants to give open-source developers a way to earn some money for contributing to important open-source projects and while helping the companies that are using those projects in key parts of their business, and it just raised $15 million to build those connections. General Catalyst, Foundry Group, and former Red Hat CEO Matthew Szulik co-led the Series A founding round into the Boston-based startup, the first time the 17-person company has taken financing, said Donald Fischer, co-founder and CEO of Tidelift. The other co-founders — Havoc Pennington, Jeremy Katz, and Luis Villa — share a wealth of open-source experience across companies like Red Hat and organizations like The Wikimedia Foundation and the Mozilla Foundation.
  • Tidelift Raises $15M Series A To Make Open Source Work Better--For Everyone

today's howto

Linux and CPU Security

  • 22 essential security commands for Linux
    There are many aspects to security on Linux systems – from setting up accounts to ensuring that legitimate users have no more privilege than they need to do their jobs. This is look at some of the most essential security commands for day-to-day work on Linux systems.
  • CVE-2018-3639: Spectre Variant 4 Vulnerability Affects the Linux Kernel
    A Spectre variant 4 vulnerability has been identified in the Linux kernel and represents a very dangerous threat to all affected machines. All system administrators are urged to apply the latest updates as soon as possible to mitigate any possible impact.
  • Spectre Number 4, STEP RIGHT UP!
    In the continuing saga of Meltdown and Spectre (tl;dr: G4/7400, G3 and likely earlier 60x PowerPCs don't seem vulnerable at all; G4/7450 and G5 are so far affected by Spectre while Meltdown has not been confirmed, but IBM documentation implies "big" POWER4 and up are vulnerable to both) is now Spectre variant 4. In this variant, the fundamental issue of getting the CPU to speculatively execute code it mistakenly predicts will be executed and observing the effects on cache timing is still present, but here the trick has to do with executing a downstream memory load operation speculatively before other store operations that the load does not depend on. If the CPU is convinced to speculatively execute down this victim path incorrectly, it will revert the stores and the register load when the mispredict is discovered, but the loaded address will remain in the L1 cache and be observable through means similar to those in other Spectre-type attacks.