Xex File Hex Dump Options

[Vayate]

If anyone cares to check it out, I've dumped the emulation profile in a hex editor. Took a couple minutes, even on my nice m,achine. Anyway, this is probably neither here nor there -- just thought I'd throw it out there and see if anyone found it useful.

You can get the 9MB .txt file on my college webspace (here)
Looks a lot different from XBE files. Much less decipherable text. Anyway, good luck -- awesome if you find something useful.

This post has been edited by Vayate: Nov 27 2005, 07:41 AM

[Neptune]

why dont you zip it...it'll compress to less then a meg

[cshah0]

that's good, now which encryption is used?

[Vayate]

Oh, it also seems that XEX files do have a bit more security than XBEs (duh). I tried to disassemble it with PVDasm 1.5, but it gave me a "File is already in use" error even after I rebooted to make 100% sure it wasn't.

This post has been edited by Vayate: Nov 29 2005, 10:06 PM

[binjinx]

Oh, it also seems that XEX files do have a bit more security than XBEs (duh). I tried to disassemble it with PVDasm 1.5, but it gave me a "File is already in use" error even after I rebooted to make 100% sure it wasn't.

wouldnt it be better to use IDA since the target cpu is ibm ( is it G core?) PVDasm dont handle that

[cshah0]

SHA-1 used in the default.xex
http://xboxhacker.net/index.php?option=com...&id=40&Itemid=2

[TSOPrano]

Didn't SHA-1 get hacked?

[bigbubba7373]

SHA-1 Broken
Posted by L33tdawg on Thursday, February 17, 2005 - 11:09 AM (Reads: 1098)

Source: Schneier on Security



--------------------------------------------------------------------------------

L33tdawg: Much love to Fyodor Yarochkin for the heads up on this


--------------------------------------------------------------------------------

SHA-1 has been broken. Not a reduced-round version. Not a simplified version. The real thing. The research team of Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu (mostly from Shandong University in China) have been quietly circulating a paper describing their results:


collisions in the the full SHA-1 in 2**69 hash operations, much less than the brute-force attack of 2**80 operations based on the hash length.
collisions in SHA-0 in 2**39 operations.
collisions in 58-round SHA-1 in 2**33 operations.
This attack builds on previous attacks on SHA-0 and SHA-1, and is a major, major cryptanalytic result. It pretty much puts a bullet into SHA-1 as a hash function for digital signatures (although it doesn't affect applications such as HMAC where collisions aren't important). The paper isn't generally available yet.

[The Dude]

This is just a shot in the dark, but could this default.xex file simply be a database/list of games on the backwards compatability list? Perhaps this file stores a list of signatures/identification numbers from each default.xbe for each game. When the .xex file runs it simply extracts and dumps the signatures for the games onto the hard drive?

This file seems way to small to store a seperate emu for every single game on the backwards compatability list. It seems more feasable the base emulator for every game is on the hdd. The xbox then reads the default.xbe from the original xbox game then cross referances the hdd to make sure the game is "authorized" to play.

On another note...

Seeing as how MS has specifically excluded known games that have been exploited, perhaps MS has made a list of games they will LET us play rather than a list of games that are really playable. Perhaps they rest of the games that aren't on the list are being investigated for possible exploits?

Of course this is just all speculation, but I thought I would throw it out there.

This post has been edited by The Dude: Dec 6 2005, 06:02 AM

[MGSolidus2]

I can't see the .txt. It says it's not available from the site.

EDIT: If what the dude says is true, then that's the key to partially cracking the 360. All we would have to do would be to use hacking programs from the 1st xbox and they would run on the 360. Actually if we used like Slayer's, and added the hacked dash to the list, then maybe we could burn it to a CD and boot it up, giving us partial FTP access to it.

DOUBLE EDIT: Nevermind, I don't think this will work, because we can't develop our own .XBE's yet.

This post has been edited by MGSolidus2: Dec 6 2005, 09:03 PM

[Darren101]

Don't worry about devving.

Get yourself an assembler, and you're done .