QUOTE(dcemuser @ Nov 17 2009, 08:05 AM)
I think you failed to understand this. They found a copy of crtl.bin in the update, but it still contains the same-old list of revoked consoles. HOWEVER, MS could use that file to store a list of banned consoles IN THE FUTURE (they currently have not, not even in "wave 5"), however, I doubt they will store 1 million Console IDs in your NAND. Just think about it for a full three seconds.
They wouldn't have to write the IDs to the NAND, they aren't trying to stop DLC sharing. The IDs would just have to be momentarily loaded into ram, so that the update could check your console ID against the list, and if it appears, would write the banning sec data to your NAND.
I'm sure it's got something to do with incredibly complicated 1-way maths, but if the ban writes the same piece of data to everyone's xbox, and people who have already gotten their cpu (from the original hack) can decrpyt that data on their consoles (if they get banned) Then once we have a clean version of the exact data, if we know the encryption method used, why can't we use those two pieces of information to reverse crack the CPU key on our consoles? I'm sure it would still take years, but with distributed computing and GPU power couldn't we start building a look-up table. encypting the image with every possible value of the CPU key, as the table grew your chance of finding a match would go up and up.