XboxHacker BBS
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
June 18, 2013, 11:27:08 PM


Login with username, password and session length


Pages: « 1 2 3
  Print  
Author Topic: default.xex  (Read 49391 times)
th0mas
Member
**
Posts: 37


View Profile WWW
« Reply #40 on: December 01, 2005, 01:17:33 PM »

hrm.. if it's not a sig, then there doesn't appear to be a signed sig in the file (unless it's just the start or end of the data at 0x2000).

Which is unlikely.  Unless I'm just not seeing it.

Anyways this is still conjecture and shouldn't really be the focus just yet Smiley
Logged

oskie
Newbie
*
Posts: 6


View Profile
« Reply #41 on: December 01, 2005, 02:07:55 PM »

I'm starting to think that the table that you th0mas found at 0x000108-0x00070b must contain the signatures... The original xbox had 1+16 signature keys (main + alternate). Here we have 47 plus one, filled with zeroes. I think that the 48th key, which is all zero, could be the LAN key (also used by the original xbox, and mentioned in the dump posted by SiliconIce). My guess is that the dword that precedes the 20byte key specifies what the key is for. If that is true, we would have the following specifier dwords:

35 * 0x00000103
 9 * 0x00000101
 1 * 0x00000041
 1 * 0x00000072
 2 * 0x00000053


Oskar
Logged
th0mas
Member
**
Posts: 37


View Profile WWW
« Reply #42 on: December 01, 2005, 05:31:24 PM »

the sig keys you speak of in the original xbe were for syslink and live encryption.  There would be no need for 47 of them.

Also, this table is not in all XEX's it seems.  Or at least, not a 48 entry table.  It seems to be related to size of encrypted data in the XEX instead.
Logged

xbox7887
Newbie
*
Posts: 5


View Profile
« Reply #43 on: December 05, 2005, 02:44:24 PM »

Has anyone tried disassembling the .xex to see what they can come up with?
« Last Edit: December 05, 2005, 05:43:44 PM by xbox7887 » Logged
pablot
Hacker
***
Posts: 79


Pleased to meet ya!


View Profile WWW
« Reply #44 on: December 05, 2005, 03:32:06 PM »

did you dissasseble that using the correct architecture? Otherwise it's pretty much bogus..

EDIT:
hmm.. missed that whole thing about the comments.. where did you get those from?
« Last Edit: December 05, 2005, 03:47:16 PM by pablot » Logged

Pleased to meet ya!
xbox7887
Newbie
*
Posts: 5


View Profile
« Reply #45 on: December 05, 2005, 04:32:38 PM »

Heh, mistakes happen ;p
« Last Edit: December 05, 2005, 05:43:24 PM by xbox7887 » Logged
pablot
Hacker
***
Posts: 79


Pleased to meet ya!


View Profile WWW
« Reply #46 on: December 05, 2005, 05:31:09 PM »

what I am confused about is: Why would the compiler leave comments in the machine code? Isn't that just something that the dissassembler comes up with?
Logged

Pleased to meet ya!
xbox7887
Newbie
*
Posts: 5


View Profile
« Reply #47 on: December 05, 2005, 05:41:33 PM »

lol yes I did a hex search for some of the comments in the disassembler I'm using and they were all in the ida.int file...sorry to get your hopes up, all of that is almost certain bogus commenting Sad.  I'll edit my posts to avoid confusion.
« Last Edit: December 05, 2005, 05:44:05 PM by xbox7887 » Logged
th0mas
Member
**
Posts: 37


View Profile WWW
« Reply #48 on: December 06, 2005, 12:47:23 AM »

Yeah.  The assembly is bogus too..  it's just interpreting the bytes, it doesn't mean that you've got meaning.
Logged

xbox7887
Newbie
*
Posts: 5


View Profile
« Reply #49 on: December 06, 2005, 09:08:32 AM »

Well that's not necessarily true, if it was disassembled correctly you would be able to see many different things...maybe even hook to code of your own to load Wink
Logged
th0mas
Member
**
Posts: 37


View Profile WWW
« Reply #50 on: December 06, 2005, 11:34:02 AM »

Well that's not necessarily true, if it was disassembled correctly you would be able to see many different things...maybe even hook to code of your own to load Wink

the assembly is bogus.  You were attempting to read it as x86 opcodes (hence the "286" references, the int xxh calls & associated comments, etc).  The actual image at 0x2000 is encrypted/compressed (now looking more likely encrypted).  the actual assembly is in a PPC format.

Anyways, the news on the frontpage right now jives more with the concept that XEX files are containers. that's by guessing the meaning of functions such as XexpLoadFile and XexpCompleteImageLoad.
Logged

xbox7887
Newbie
*
Posts: 5


View Profile
« Reply #51 on: December 06, 2005, 12:59:23 PM »

Yeah theres no way in hell to disassemble a decrypted archive file ;x.  The info in the front page is very interesting, hopefully some more will be figured out.
Logged
Pages: « 1 2 3
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM