<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynamic Tardos Traitor Tracing Schemes · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1111.3597/</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/1111.3597/feed.xml" rel="self" type="application/rss+xml" /><item><title>Dynamic Tardos Traitor Tracing Schemes — mentioned by coppsilgold</title><link>https://news.ycombinator.com/item?id=46713614</link><guid isPermaLink="false">urn:hackerpapers:mention:1111.3597:46713614</guid><pubDate>Thu, 22 Jan 2026 00:24:15 GMT</pubDate><description>&lt;p&gt;While useful it needs a big red warning to potential leakers. If they were personally served documents (such as via email, while logged in, etc) there really isn&amp;#x27;t much that can be done to ascertain the safety of leaking it. It&amp;#x27;s not even safe if there are two or more leakers and they &amp;quot;compare notes&amp;quot; to try and &amp;quot;clean&amp;quot; something for release. https://en.wikipedia.org/wiki/Traitor_tracing#Watermarking https://arxiv.org/abs/1111.3597 The watermark can even be contained in the wording itself (multiple versions of sentences, word choice etc stores the entropy). The only moderately safe thing to…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1111.3597/"&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>
