<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DifFuzz: Differential Fuzzing for Side-Channel Analysis · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1811.07005/</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/1811.07005/feed.xml" rel="self" type="application/rss+xml" /><item><title>DifFuzz: Differential Fuzzing for Side-Channel Analysis — mentioned by openasocket</title><link>https://news.ycombinator.com/item?id=19171825</link><guid isPermaLink="false">urn:hackerpapers:mention:1811.07005:19171825</guid><pubDate>Fri, 15 Feb 2019 15:50:23 GMT</pubDate><description>&lt;p&gt;Side-channel attacks are some of the most terrifying to me, because fundamentally your code works fine, it&amp;#x27;s just some detail in the timing that gives away information. At least with buffer overflows there are automated ways to try and find them, like fuzz testing. It&amp;#x27;s not perfect, but at least it&amp;#x27;s something to try and validate you are doing the right thing. Is there some sort of fuzz testing that could potentially find side-channel timing attacks? Maybe some sort of statistical analysis on the timing results? I found this https://arxiv.org/pdf/1811.07005.pdf but it seems to be fairly…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1811.07005/"&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>
