Posted 14 May 2019 - 10:43 PM
For the things we have to learn before we can do them, we learn by doing them.
Posted 15 May 2019 - 04:23 AM
This also means Linux-based containers and VMs are also open to attack. To protect yourself, you'll need to patch the following Linux files: Kernel, kernel-rt, libvirt, qemu-kvm, qemu-kvm-rhev, and microcode_clt on all your systems. In particular, there's a known attack vector for CE-2018-12130, which enables a malicious VM or container spy another containers or VMs. In other words, you must patch all your running containers and VMs on a server -- or one bad apple can reveal the data in the patched ones.
To defend yourself, your processor must be updated, your operating system must be patched, and for the most protection, Hyper-Threading disabled. When Meltdown and Spectre showed up, the Linux developers were left in the dark and scrambled to patch Linux. This time, they've been kept in the loop.
You'll never need to install it again
"I did and I'm really happy"
Posted 15 May 2019 - 09:13 AM
Configs/PGP Key/comhack π ∞
"Do you begin to see, then, what kind of world we are creating? It is the exact opposite of the stupid hedonistic Utopias that the old reformers imagined. A world of fear and treachery and torment, a world of trampling and being trampled upon, a world which will grow not less but more merciless as it refines itself. Progress in our world will be progress toward more pain." -George Orwell, 1984
Posted 15 May 2019 - 02:52 PM
Also tagged with one or more of these keywords: intel, cpu vulnerability
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users