[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Home]
Board
Settings Home
/g/ - Technology



Thread archived.
You cannot reply anymore.



File: EEF9jcl.gif (1.51 MB, 425x481)
1.51 MB
1.51 MB GIF
There is one way to save yourself from this mess.

>Own AMD CPU with SME support.
>Enable SME, preferably with separately encrypted VM pages.
>Have kernel support for SME.

The only thing left to do is to start encrypting hot RAM to prevent speculative page peeping.
Only AMD Pro and Epyc support the SME feature.
Talos II WS is also a good safe bet against the bug.

Did Keller see this from the start...? Is that why they created SME?
>>
You are a boring person and there is nothing on your computer that anyone will seek to find. Enterprise systems are pretty fucked though.
>>
>>64132333
People have crypto.
Any computer is worth a scan for private keys in memory.

AWS isn't even fucking patched yet.

Everything is fire right now.




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.