Thread replies: 11
Thread images: 2
Thread images: 2
File: ^851EC32101F4BBE0E45A93C1C59E0CDC05388C6BBCA469B1A6^pimgpsh_fullsize_distr.jpg (90KB, 774x753px) Image search:
[Google]
90KB, 774x753px
http://thehackernews.com/2016/10/linux-kernel-exploit.html
>Earlier this week, Linus Torvalds admitted that 11 years ago he first spotted this issue and also tried to fix it, but then he left it unpatched because at the time it was hard to trigger.
LINKEKS BTFO LMFAO
>>
File: 1448711210554.jpg (33KB, 629x368px) Image search:
[Google]
33KB, 629x368px
>linux
>secure
>>
>windows
>secure
>>
>OS X/macOS
>secure
>>
>>57249378
It's a local exploit.
Unless you have access to the machine it's pretty hard to replicate.
>>
>>57249967
Fucking nothing then
If someone has physical access to your machine, they can just pull out the RAM and hard drive, and gather more than enough data for any malicious purposes
>>
>>57249967
Dirty cow OBTF
>(overblown to fuck)
>>
>Linus Torvalds sold backdoor to NSA
nothing new
>>
>>57250134
Pull out the... RAM, anon? The volatile memory? The thing that wipes itself when no power?
But yeah if you need physical access to the machine to do this, though shit.
>>
>he fell for the bare metal Linux meme
>>
>>57251160
https://www.deepdotweb.com/jolly-rogers-security-guide-for-beginners/cold-boot-attacks-unencrypted-ram-extraction/
A shit article but i don't have time to find anything better right now. You are kind of right but not exactly, someone with access could gain much info from the RAM on your machine.
Not mentioning that someone could gain all info about your machine by getting their hands on it , without such 11 years old exploit. I mean , this is nothing compared to being able to login to every windows machine just with the use of a recovery console from an windows install disk.
Thread posts: 11
Thread images: 2
Thread images: 2