<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ozone: Efficient Execution with Zero Timing Leakage for Modern Microarchitectures · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1703.07706/</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/1703.07706/feed.xml" rel="self" type="application/rss+xml" /><item><title>Ozone: Efficient Execution with Zero Timing Leakage for Modern Microarchitectures — mentioned by nickpsecurity</title><link>https://news.ycombinator.com/item?id=18143852</link><guid isPermaLink="false">urn:hackerpapers:mention:1703.07706:18143852</guid><pubDate>Thu, 04 Oct 2018 21:31:29 GMT</pubDate><description>&lt;p&gt;I considered doing it just to run security-critical apps on CPU&amp;#x27;s like CHERI that I couldn&amp;#x27;t get in ASIC form: https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ Slow, $2000-a-unit hardware might be worth it if it makes your OS close to unhackable. I&amp;#x27;d just have to make sure apps are lean and efficient. I already favor those, though. :) Also, there&amp;#x27;s been work in &amp;quot;instruction set randomization&amp;quot; that obfuscates the CPU itself to reduce odds malware will work. Mostly widely-deployed, non-custom attacks but might stop some custom attackers, too.…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1703.07706/"&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>Ozone: Efficient Execution with Zero Timing Leakage for Modern Microarchitectures — mentioned by nickpsecurity</title><link>https://news.ycombinator.com/item?id=17558343</link><guid isPermaLink="false">urn:hackerpapers:mention:1703.07706:17558343</guid><pubDate>Wed, 18 Jul 2018 13:53:39 GMT</pubDate><description>&lt;p&gt;Interesting. I&amp;#x27;m mostly not tracking these since there is a ton of CompSci work post-Meltdown/Spectre. I do periodically look for things that try to stop many attacks at once. Here&amp;#x27;s two I found that were interesting with one in hardware and one for clouds on top of a verified hypervisor: https://arxiv.org/pdf/1703.07706.pdf https://pdfs.semanticscholar.org/6aa3/18e95cae5a932e330857e5...&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1703.07706/"&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>Ozone: Efficient Execution with Zero Timing Leakage for Modern Microarchitectures — mentioned by nickpsecurity</title><link>https://news.ycombinator.com/item?id=17537508</link><guid isPermaLink="false">urn:hackerpapers:mention:1703.07706:17537508</guid><pubDate>Sun, 15 Jul 2018 22:41:46 GMT</pubDate><description>&lt;p&gt;Language-based Information Flow Security (2003) http://www.cs.cornell.edu/andru/papers/jsac/sm-jsac03.pdf Note: This is a great overview with plenty of terms you can use to find modern work. It&amp;#x27;s branching out in all these areas. Key words to use include &amp;quot;non-interference&amp;quot;, &amp;quot;static analysis,&amp;quot; &amp;quot;covert channels,&amp;quot; &amp;quot;labels,&amp;quot; &amp;quot;confidentiality,&amp;quot; and &amp;quot;side channels.&amp;quot; Securing Information Flow at Runtime (2008) http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.142.... Note: Example of the language work they do to lay down foundations. Static, Info-Flow Analysis That Handles Implicit Flows…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1703.07706/"&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>
