<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Joining The AACS Fiasco</title>
	<atom:link href="http://www.gringod.com/2007/05/03/joining-the-aacs-fiasco/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gringod.com/2007/05/03/joining-the-aacs-fiasco/</link>
	<description>Randomised nonsense.</description>
	<lastBuildDate>Fri, 04 Nov 2011 08:49:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: GrinGod [dot] Com &#187; Blog Archive &#187; Everybody Needs A Number</title>
		<link>http://www.gringod.com/2007/05/03/joining-the-aacs-fiasco/comment-page-1/#comment-18096</link>
		<dc:creator>GrinGod [dot] Com &#187; Blog Archive &#187; Everybody Needs A Number</dc:creator>
		<pubDate>Thu, 10 May 2007 21:30:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.gringod.com/2007/05/03/joining-the-aacs-fiasco/#comment-18096</guid>
		<description>[...] As I previously blogged, the AACS-LA has a 128bit hex number that they call their own, and nobody else can use it without their expressed permission. If anyone does use it then the AACS-LA can use the power of the DMCA to stop its use and sue the people that used it, if they so wish. What gives the AACS-LA the rights to do this is that the number is used for the encryption of data (on HD-DVD and Blueray discs). [...]</description>
		<content:encoded><![CDATA[<p>[...] As I previously blogged, the AACS-LA has a 128bit hex number that they call their own, and nobody else can use it without their expressed permission. If anyone does use it then the AACS-LA can use the power of the DMCA to stop its use and sue the people that used it, if they so wish. What gives the AACS-LA the rights to do this is that the number is used for the encryption of data (on HD-DVD and Blueray discs). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Guard</title>
		<link>http://www.gringod.com/2007/05/03/joining-the-aacs-fiasco/comment-page-1/#comment-17862</link>
		<dc:creator>Damien Guard</dc:creator>
		<pubDate>Thu, 03 May 2007 07:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.gringod.com/2007/05/03/joining-the-aacs-fiasco/#comment-17862</guid>
		<description>If it&#039;s anything like DVD then the content is encrypted with a &#039;volume&#039; key that changes per disc.  The volume key is on the disc a few hundred times, each encrypted with a &#039;vendor&#039; key.

The idea was that should a vendor key become compromised then they would pull it from future discs and issue the vendor with one of the new spare keys already in use on all the discs.

The upshot would be that discs would continue to play everywhere except new discs would not play in compromised players. Obviously updating PowerDVD and WinDVD to use new keys is a lot easier than shipping a firmware update to thousands of set-top player owners so I&#039;m not sure they ever revoked those keys.

The problem with the DVD hack is that they broke the encryption in such a way that they uncovered *all* the vendor keys.

I would imagine the situation is similar with AACS.

[)amien</description>
		<content:encoded><![CDATA[<p>If it&#8217;s anything like DVD then the content is encrypted with a &#8216;volume&#8217; key that changes per disc.  The volume key is on the disc a few hundred times, each encrypted with a &#8216;vendor&#8217; key.</p>
<p>The idea was that should a vendor key become compromised then they would pull it from future discs and issue the vendor with one of the new spare keys already in use on all the discs.</p>
<p>The upshot would be that discs would continue to play everywhere except new discs would not play in compromised players. Obviously updating PowerDVD and WinDVD to use new keys is a lot easier than shipping a firmware update to thousands of set-top player owners so I&#8217;m not sure they ever revoked those keys.</p>
<p>The problem with the DVD hack is that they broke the encryption in such a way that they uncovered *all* the vendor keys.</p>
<p>I would imagine the situation is similar with AACS.</p>
<p>[)amien</p>
]]></content:encoded>
	</item>
</channel>
</rss>

