<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MemJam: A False Dependency Attack against Constant-Time Crypto Implementations · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1711.08002/</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/1711.08002/feed.xml" rel="self" type="application/rss+xml" /><item><title>MemJam: A False Dependency Attack against Constant-Time Crypto Implementations — mentioned by ChrisLomont</title><link>https://news.ycombinator.com/item?id=31751472</link><guid isPermaLink="false">urn:hackerpapers:mention:1711.08002:31751472</guid><pubDate>Wed, 15 Jun 2022 11:28:41 GMT</pubDate><description>&lt;p&gt;&amp;gt; Constant time&amp;quot; in cryptography means that there is no information flow from secrets to timings If &amp;quot;constant time&amp;quot; cryptography were achievable don&amp;#x27;t you think we&amp;#x27;d have it and there&amp;#x27;d be no more timing attacks breaking encryption schemes? &amp;quot;Constant time&amp;quot; cryptography is a mathematical abstraction, a goal, like &amp;quot;unbreakable cipher&amp;quot; and &amp;quot;unbreakable hash&amp;quot; and &amp;quot;frictionless surface.&amp;quot; They don&amp;#x27;t occur in practice. This article breaks itself breaks a &amp;quot;constant time&amp;quot; cryptography with a timing attack. The problem is, as this paper demonstrates (along with many others) coding up a constant time…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1711.08002/"&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>
