{"id":131,"date":"2011-02-22T18:00:35","date_gmt":"2011-02-22T17:00:35","guid":{"rendered":"http:\/\/cerezo.name\/blog\/?p=131"},"modified":"2024-10-14T14:28:46","modified_gmt":"2024-10-14T12:28:46","slug":"traitor-tracing-theory-vs-practice","status":"publish","type":"post","link":"http:\/\/cerezo.name\/blog\/2011\/02\/22\/traitor-tracing-theory-vs-practice\/","title":{"rendered":"Traitor Tracing: Theory vs Practice"},"content":{"rendered":"

An efficient public key traitor tracing scheme<\/a><\/p>\n

We construct a public key encryption scheme in which there is one public encryption key, and many<\/em> private decryption keys. If a broadcaster encrypts once with the public key, then each legitimate receiver can decrypt with a different private key. If a coalition of receivers collude to create a new decryption key then there is an efficient algorithm to trace the new key to its creators. Hence, our system provides a simple and efficient solution to the \u201ctraitor tracing problem\u201d. Our tracing algorithm is deterministic, and catches all<\/em> active traitors while never<\/em> accusing innocent users, although it is only partially \u201cblack box\u201d. A minor modification to the scheme enables it to resist an adaptive chosen ciphertext attack. Our techniques apply error correcting codes to the discrete log representation problem.<\/em><\/p>\n

The most cited traitor tracing crypto-scheme<\/a> versus\u2026 the Black Sunday hack<\/a>:<\/p>\n

Among the countermeasures he says he created was one known among pirates as the \u201cBlack Sunday\u201d kill<\/a> \u2014 an elaborate scheme that destroyed tens of thousands of pirate DirecTV cards<\/strong> a week before Super Bowl Sunday in 2001.<\/em><\/p>\n

Instead of being delivered all at once like other measures, the Black Sunday attack code was sent to pirate cards in about five dozen parts over the course of two months, like a tank transported piece by piece to a battlefield to be assembled in the field. <\/strong>\u201cThey never expected us to do this,\u201d Tarnovsky says.<\/em><\/p>\n

Why stop at tracing traitors when you can wipe them out<\/em>? Very clever.<\/p>\n","protected":false},"excerpt":{"rendered":"

An efficient public key traitor tracing scheme We construct a public key encryption scheme in which there is one public encryption key, and many private decryption keys. If a broadcaster encrypts once with the public key, then each legitimate receiver can decrypt with a different private key. If a coalition of receivers collude to create [\u2026]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"ngg_post_thumbnail":0},"categories":[6],"tags":[],"_links":{"self":[{"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts\/131"}],"collection":[{"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/comments?post=131"}],"version-history":[{"count":7,"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts\/131\/revisions"}],"predecessor-version":[{"id":1673,"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/posts\/131\/revisions\/1673"}],"wp:attachment":[{"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/media?parent=131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/categories?post=131"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/cerezo.name\/blog\/wp-json\/wp\/v2\/tags?post=131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}