Feed aggregator

Fedora 28: runc Security Update

LinuxSecurity.com - Sat, 01/26/2019 - 19:35
Categories: Linux

Fedora 28: haproxy Security Update

LinuxSecurity.com - Sat, 01/26/2019 - 19:35
Categories: Linux

Fedora 29: runc Security Update

LinuxSecurity.com - Sat, 01/26/2019 - 19:35
Categories: Linux

Fedora 29: haproxy Security Update

LinuxSecurity.com - Sat, 01/26/2019 - 19:35
Categories: Linux

Ubuntu 3869-1: Subversion vulnerability

LinuxSecurity.com - Sat, 01/26/2019 - 19:35
Categories: Linux

A digital DC power supply -- part 3: command control from the PC

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Guido Socher
Categories: Linux

Computer Assisted Simulation of DNA using Linux and Perl

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Carlos Andrés Pérez
Categories: Linux

Automate the creation of graphs with Graphviz

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Jean-Etienne Poirrier
Categories: Linux

LF Tip: #defines for writing portable C-code

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Guido Socher
Categories: Linux

A digital DC power supply -- part 2: the software

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Guido Socher
Categories: Linux

Book review: The Linux Enterprise Cluster

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Tom Uijldert
Categories: Linux

LF Tip: USB mice and laptops

LinuxFocus.org - Sun, 01/06/2019 - 10:35
by Guido Socher
Categories: Linux

Google denies altering YouTube code to break Microsoft Edge

OSNews.com - Thu, 12/20/2018 - 13:26
A former Microsoft intern has revealed details of a YouTube incident that has convinced some Edge browser engineers that Google added code to purposely break compatibility. In a post on Hacker News, Joshua Bakita, a former software engineering intern at Microsoft, lays out details and claims about an incident earlier this year. Microsoft has since announced the company is moving from the EdgeHTML rendering engine to the open source Chromium project for its Edge browser. [...] Google disputes Bakita's claims, and says the YouTube blank div was merely a bug that was fixed after it was reported. "YouTube does not add code designed to defeat optimizations in other browsers, and works quickly to fix bugs when they're discovered," says a YouTube spokesperson in a statement to The Verge. "We regularly engage with other browser vendors through standards bodies, the Web Platform Tests project, the open-source Chromium project and more to improve browser interoperability." While we're unlikely to ever know the real story behind this particular incident, I don't doubt for a second that Google would do something like this.

Syndicate content
Comment