Hello, I was wondering if anyone could explain exactly what happens to an 360 executable when it gets signed? Does the whole file change completely or do only certain parts change?
I'm not entirely sure (and please don't flame me if i'm wrong), but wouldn't it be possible for us to re-construct their MS's private key by comparing a signed executable with it's unsigned counterpart?
We could figure out exactly what happens to the file and try to reconstruct it!
Also, I was wondering if it would be possible to modify the 360 to use a different key? I understand the whole private / public keypair system and going by this the 360 needs to know the public key. Obviously it needs to store it somewhere. Doesn't that mean that we could create our own keypair and "re-program" the 360 to use it? It really would depend on where the console stored the key and how strongly it was encrypted.