It's no longer necessary to run attacker code on the victim system.
Newsflash
Linux 4.18: Raspi-3-Support und Vorboten neuer Firewall-Technik
Highlights von Linux 4.18 sind Support für USB 3.2, Anfänge eines neuen
Firewall-Ansatzes, neue Grafiktreiber und Verbesserungen zur Live-Migration von
VMs.
32-bit ARM Finally Gets Mitigated For Spectre V1/V2 With Linux 4.18
While
64-bit ARM (AArch64) has been mitigated for months with the mainline Linux
kernel against Spectre Variant One and Two, with the Linux 4.18
kernel is finally Spectre V1/V2 treatment for 32-bit ARM.
Why it's not a good idea to handle evdev directly
Gather
round children, it's story time. Especially for you children who lurk on
linux and think you may learn something there. Today, I'll tell you a horror
story. The one where we convert kernel input events into touchpad events, with
the subtle subtitle of "friends don't let friends handle evdev events".
DARPA Plans a Major Remake of U.S. Electronics
The
defense department’s research wing is pouring $1.5 billion into projects that
could radically alter how electronics are made.
(Video) Sexy Linux Task States
Why "sexy" Linux task states?
How Energy Aware Scheduling helps make the Google Pixel the fastest Android phone
Far back in the past when Linux was just an idea in the mind of Linus Torvalds, CPUs were single-core entities which required an immense amount of energy for little power. The first ever commercially available processor, the Intel 4004, ran at a clock-rate of 740kHz on a single core. Back then, there was no need for a load scheduler. Load scheduling was reserved for the dual-core “behemoths” such as the IBM Power 4 which came out some decades after. These ran at a beastly 1.1GHz to 1.9GHz and required programs and the system to utilize these cores correctly. How did we get from these machines to software algorithms that make use of multiple cores? You may have heard of Energy Aware Scheduling (EAS) before.
