
) from the developer itself for the program and subroutine-programs inside this .xbe.
This userkey (and or alternative userkey's) are enclosed into this header, and so yes, these custom hashes are MS signed too.
We can't change those, because then MS signing is no valid anymore, and the kernal just refuses to execute this file.
Back to the DATA inside an .xbe.
This data is put AFTER the MS signed headerinfo.
If you look at the data, it's just build up with the main program; signed with the main user SHA1 hash key. And also much with extra programs; like DX8D3 routines, save/load etc. Those are also signed with SHA1 hash (the alternative ones)
An SHA1 hash is calculated by a certain databytes as a block. If you change the length of a datablock, the hash is also changed as well..... AND the MS signing is not valid anymore also; because the total .xbe filelength is not the same anymore.
But if you manage to keep a block exact the same bytes lenght, it must be possible to generate a so called HASH collision. This means that the hash of the original datablock = the same as the altered datablock; including our program in to te startpart.
Because there are always extra bytes available to get a block a certain length; theoreticly it should be possible to change those such that the HASH is the same again as the original (MS signed into the header!)
////
The methods described for MD5 (looks like SHA1 hashing protocol) it must be possible to generate such a hash collison, say in maximum 2^40 till 2^50 possible combinations to try.
This MUST be possible with common hardware. (MS hashing is 2^1024 possibilities to give an idea!!!!). And within a few weeks, months max.
So yeh, i think it must be possible this way.
I'm starting to write a bootloader now. I like to get help here, because it is goiing my first Xbox program...
Alos I'm reading a lot about cryptology methods etc. just to learn and think how things exactly work.
Exploits are still very fine for the meantime; but those could be always circumvented by MS with a new kernal, new dash etc.
Above hack is very, very difficult for MS to get a workaraund for it...
I hope that in thge maentime new exploitable .xbe were found. The progframs on DVD's are interesting here