<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploring Widevine for Fun and Profit · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2204.09298/</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/2204.09298/feed.xml" rel="self" type="application/rss+xml" /><item><title>Exploring Widevine for Fun and Profit — mentioned by FreakLegion</title><link>https://news.ycombinator.com/item?id=33146903</link><guid isPermaLink="false">urn:hackerpapers:mention:2204.09298:33146903</guid><pubDate>Mon, 10 Oct 2022 01:27:19 GMT</pubDate><description>&lt;p&gt;Widevine has been broken at least a few times, including by recovering the private key from its white-box implementation: https://github.com/tomer8007/widevine-l3-decryptor/wiki/Reve.... Note that the write-up says it was the &amp;quot;old&amp;quot; version, but that&amp;#x27;s relative to the date of the write-up. Google overhauled Widevine after he broke it. I&amp;#x27;m less familiar with shielding data like this, but historically things like VMProtect and Themida were the standard for shielding programs. These offer a degree of resistance to automation, but a determined human will eventually figure them out, and then…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2204.09298/"&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>
