High-bandwidth Digital Content Protection

1 week ago 5

Master key release: filled in the author's name

← Previous revision Revision as of 04:07, 5 July 2025
Line 61: Line 61:


=== Master key release ===
=== Master key release ===
On 14 September 2010, [[Engadget]] reported the release of a possible genuine HDCP master key which can create device keys that can authenticate with other HDCP compliant devices without obtaining valid keys from The Digital Content Protection LLC. This master key would neutralize the key revocation feature of HDCP, because new keys can be created when old ones are revoked.<ref name="Lawler"/> Since the master key is known, it follows that an unlicensed HDCP decoding device could simply use the master key to dynamically generate new keys on the fly, making revocation impossible. It was not immediately clear who discovered the key or how they discovered it, though the discovery was announced via a [[Twitter]] update which linked to a [[Pastebin]] snippet containing the key and instructions on how to use it. Engadget said the attacker may have used the method proposed by Crosby in 2001 to retrieve the master key, although they cited a different researcher. On 16 September, Intel confirmed that the code had been cracked.<ref>{{cite news| url=http://www.foxnews.com/scitech/2010/09/16/intel-confirms-hdtv-code-cracked/ | archive-url=https://web.archive.org/web/20100917184417/http://www.foxnews.com/scitech/2010/09/16/intel-confirms-hdtv-code-cracked/ | url-status=dead | archive-date=17 September 2010 | work=Fox News | title=HDTV Code Crack Is Real, Intel Confirms | date=16 September 2010}}</ref><ref>{{Cite web|url=https://www.tomshardware.com/news/hdcp-master-key-copy-protection,11311.html|title=Intel Confirms That HDCP Master Key is Cracked|author1=Marcus Yam|date=18 September 2010|website=Tom's Hardware}}</ref> Intel has threatened legal action against anyone producing hardware to circumvent the HDCP, possibly under the DMCA.<ref name=w2/>
On 14 September 2010, [[Engadget]] reported the release of a possible genuine HDCP master key which can create device keys that can authenticate with other HDCP compliant devices without obtaining valid keys from The Digital Content Protection LLC. This master key would neutralize the key revocation feature of HDCP, because new keys can be created when old ones are revoked.<ref name="Lawler"/> Since the master key is known, it follows that an unlicensed HDCP decoding device could simply use the master key to dynamically generate new keys on the fly, making revocation impossible. It was not immediately clear who discovered the key or how they discovered it, though the discovery was announced via a [[Twitter]] update which linked to a [[Pastebin]] snippet containing the key and instructions on how to use it. Engadget said the attacker may have used the method proposed by Crosby in 2001 to retrieve the master key, although they cited a different researcher. On 16 September, Intel confirmed that the code had been cracked.<ref>{{cite news | first=Jeremy A. | last=Kaplan | url=http://www.foxnews.com/scitech/2010/09/16/intel-confirms-hdtv-code-cracked/ | archive-url=https://web.archive.org/web/20100917184417/http://www.foxnews.com/scitech/2010/09/16/intel-confirms-hdtv-code-cracked/ | url-status=dead | archive-date=17 September 2010 | work=[[Fox News]] | title=HDTV Code Crack Is Real, Intel Confirms | date=16 September 2010}}</ref><ref>{{Cite web |url=https://www.tomshardware.com/news/hdcp-master-key-copy-protection,11311.html |title=Intel Confirms That HDCP Master Key is Cracked|first1=Marcus |last1=Yam |date=18 September 2010 |website=[[Tom's Hardware]]}}</ref> Intel has threatened legal action against anyone producing hardware to circumvent the HDCP, possibly under the DMCA.<ref name=w2/>
<!-- TO WOULD-BE EDITORS: Please do not add the text of the master key (a possible violation of [[WP:COPYVIO]]). Including a link to the key is disputed as well. See talk page. -->
<!-- TO WOULD-BE EDITORS: Please do not add the text of the master key (a possible violation of [[WP:COPYVIO]]). Including a link to the key is disputed as well. See talk page. -->


Open Full Post