<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secure Encrypted Virtualization is Unsecure · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1712.05090/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1712.05090/feed.xml" rel="self" type="application/rss+xml" /><item><title>Secure Encrypted Virtualization is Unsecure — mentioned by rstuart4133</title><link>https://news.ycombinator.com/item?id=26406913</link><guid isPermaLink="false">urn:hackerpapers:mention:1712.05090:26406913</guid><pubDate>Wed, 10 Mar 2021 02:04:01 GMT</pubDate><description>&lt;p&gt;We already have AMD&amp;#x27;s Secure Encrypted Virtualization (SEV). If you trust AMD, you can have a secure VM running on that CPU that&amp;#x27;s totally opaque to the person who owns the CPU. So even if the KGB could own the CPU, and the USA&amp;#x27;s president could use a VM on it in full confidence the KGB wouldn&amp;#x27;t know what calculations he&amp;#x27;s using it for. What&amp;#x27;s more it runs existing software, at full speed. Well, that&amp;#x27;s the theory anyway. In practice, researchers say modifying the encrypted memory, then running the program and seeing what happens next reveals something, enough to get them root in fact. [0] But…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1712.05090/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Secure Encrypted Virtualization is Unsecure — mentioned by frankjr</title><link>https://news.ycombinator.com/item?id=23831824</link><guid isPermaLink="false">urn:hackerpapers:mention:1712.05090:23831824</guid><pubDate>Tue, 14 Jul 2020 13:41:56 GMT</pubDate><description>&lt;p&gt;Another paper that mentions AES in the ECB mode is &amp;quot;Secure Encrypted Virtualization is Unsecure!&amp;quot; [0] [0] https://arxiv.org/pdf/1712.05090.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1712.05090/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Secure Encrypted Virtualization is Unsecure — mentioned by ENOTTY</title><link>https://news.ycombinator.com/item?id=23469377</link><guid isPermaLink="false">urn:hackerpapers:mention:1712.05090:23469377</guid><pubDate>Tue, 09 Jun 2020 18:39:07 GMT</pubDate><description>&lt;p&gt;SEV has been subjected to its own share of attacks (and design/implementation fails), but note that it has a different threat model. * https://arxiv.org/pdf/1712.05090.pdf 2017 * https://arxiv.org/pdf/1612.01119.pdf 2017 * https://arxiv.org/pdf/1805.09604.pdf 2018 * https://ipads.se.sjtu.edu.cn/_media/publications/fidelius_hp... 2018 * https://seclists.org/fulldisclosure/2019/Jun/46 2019 * https://www3.cs.stonybrook.edu/~mikepo/papers/severest.asiac... 2019 * https://www.usenix.org/system/files/sec19-li-mengyuan_0.pdf 2019 * https://arxiv.org/pdf/1908.11680.pdf 2019 *…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1712.05090/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
