Language Selection

English French German Italian Portuguese Spanish

To adepts of HAL, D-BUS and complexity: be happy, it's all crap anyway

Filed under
Linux

Linux is already "the next Windows": unnecessarily complex, and therefore buggy.

The dilemma To 5.1 or not to 5.1? came after More adventures with StartCom Enterprise Linux AS-5.0.1, which in turn came after some Troubles with StartCom Enterprise Linux AS-5.0.1, which followed a restless history of distro-hopping, which only seemed to end into a RHEL5 clone.

RHEL5 clones work reasonably well, and when they work, they're stable. Now that Red Hat Enterprise Linux 5.1 was released, and StartCom was the first (currently, the only one) to have rebuilt a trademark-clean clone, I noticed that for the time being, there is at least one difference between "5.0 + all the updates" and "5.1": a new kernel (kernel 2.6.18-53) that is not present yet in the updates repositories of CentOS, Scientific Linux and X/OS. Some other differences might also exist, but I simply don't want to dig into that.

And 5.1 is breaking something that worked with 5.0.

More Here




More in Tux Machines

Games: Ostriv, Back to Bed, EVERSPACE, Hiveswap: Act 1

Openwashing and Microsoft FUD

BlueBorne Vulnerability Is Patched in All Supported Ubuntu Releases, Update Now

Canonical released today new kernel updates for all of its supported Ubuntu Linux releases, patching recently discovered security vulnerabilities, including the infamous BlueBorne that exposes billions of Bluetooth devices. The BlueBorne vulnerability (CVE-2017-1000251) appears to affect all supported Ubuntu versions, including Ubuntu 17.04 (Zesty Zapus), Ubuntu 16.04 LTS (Xenial Xerus) up to 16.04.3, Ubuntu 14.04 LTS (Trusty Tahr) up to 14.04.5, and Ubuntu 12.04 LTS (Precise Pangolin) up to 12.04.5. Read more

Security: Updates, 2017 Linux Security Summit, Software Updates for Embedded Linux and More

  • Security updates for Tuesday
  • The 2017 Linux Security Summit
    The past Thursday and Friday was the 2017 Linux Security Summit, and once again I think it was a great success. A round of thanks to James Morris for leading the effort, the program committee for selecting a solid set of talks (we saw a big increase in submissions this year), the presenters, the attendees, the Linux Foundation, and our sponsor - thank you all! Unfortunately we don't have recordings of the talks, but I've included my notes on each of the presentations below. I've also included links to the slides, but not all of the slides were available at the time of writing; check the LSS 2017 slide archive for updates.
  • Key Considerations for Software Updates for Embedded Linux and IoT
    The Mirai botnet attack that enslaved poorly secured connected embedded devices is yet another tangible example of the importance of security before bringing your embedded devices online. A new strain of Mirai has caused network outages to about a million Deutsche Telekom customers due to poorly secured routers. Many of these embedded devices run a variant of embedded Linux; typically, the distribution size is around 16MB today. Unfortunately, the Linux kernel, although very widely used, is far from immune to critical security vulnerabilities as well. In fact, in a presentation at Linux Security Summit 2016, Kees Cook highlighted two examples of critical security vulnerabilities in the Linux kernel: one being present in kernel versions from 2.6.1 all the way to 3.15, the other from 3.4 to 3.14. He also showed that a myriad of high severity vulnerabilities are continuously being found and addressed—more than 30 in his data set.
  • APNIC-sponsored proposal could vastly improve DNS resilience against DDoS