Print

[wolrahnaes]

I'm thinking that a web app for resigning the saves to a different HD key might be a solution.  It could work like this:

1. User uploads .zip of save along with filling in the relevant HD keys through a web form
2. Save is verified to be already legitimately signed (to prevent cheaters of course)
3. Save is re-signed to work with new HD key
4. Save is sent back to user as a file download

Depending on how complex the signing and verification process is and how much data needs to be transferred, this could be done in one HTTP transaction.

If someone in the know can tell me how to sign (I'm not asking for the key, just the algorithm) I could probably implement it as a web program in PHP using the non-online auth for patched XBEs and hand off the software to someone with the key, who could then change out the key and host it.

In theory that method would be secure, since it would never mean running code that knows the key on a user's computer.  The key would remain securely in the hands of those who already know it.

Just thinking out loud here, but if anyone can help me out here, maybe we can get something useful going.

[brienj]

QUOTE(wolrahnaes @ Jun 15 2005, 01:30 AM)

I'm thinking that a web app for resigning the saves to a different HD key might be a solution.  It could work like this:

1. User uploads .zip of save along with filling in the relevant HD keys through a web form
2. Save is verified to be already legitimately signed (to prevent cheaters of course)
3. Save is re-signed to work with new HD key
4. Save is sent back to user as a file download

Depending on how complex the signing and verification process is and how much data needs to be transferred, this could be done in one HTTP transaction.

If someone in the know can tell me how to sign (I'm not asking for the key, just the algorithm) I could probably implement it as a web program in PHP using the non-online auth for patched XBEs and hand off the software to someone with the key, who could then change out the key and host it.

In theory that method would be secure, since it would never mean running code that knows the key on a user's computer.  The key would remain securely in the hands of those who already know it.

Just thinking out loud here, but if anyone can help me out here, maybe we can get something useful going.

That's actually not a bad idea, my only problem with that is that I don't know how secure any of that would be, although I suppose it could be ran on a Linux server.  

[SniperKilla]

QUOTE(brienj @ Jun 15 2005, 01:43 PM)

That's actually not a bad idea, my only problem with that is that I don't know how secure any of that would be, although I suppose it could be ran on a Linux server. 

of course its a bad idea.. they dont need it.. if they want to transfer saves then use the non live authkey and xbe and resign it that way.. all its going to do is add more possibility of the authkey getting out

[therealmikeg]

I know you guys are very much not cool with the idea of the actual Auth Key getting out and you have stated that you can edit a lot with it.

Would you mind sharing what this would let you edit other than the paint?  Are we talking actual car performance here?

[esgr_pt]

QUOTE

Thanks to BrienJ, everyone can make changes to their gamesaves and even import their own templates with the PPF applied to their default.xbe and saves signed with the 'Non-XBL Auth Key'.

http://home.insightb...za-ppf-NTSC.zip

THIS WILL NOT ALLOW CUSTOM DESIGNS/HACKED GAMESAVES ONLINE!

And the keys for game signing:

QUOTE

Forza Offline Resign Info

[4D53006E_3]
ID=[4D53006E]
Title=Forza Motorsport Texture File
SigKey=DD46A68DB08C6B0086FDE4F198E0C656
AuthKey=31A43F9B548DB278EF1D0AF8E74BD5B016324526
DataFile=new.texture
SigOffset=-20
DataOffset=0
DataLen=-20

[4D53006E_4]
ID=[4D53006E]
Title=Forza Motorsport Package File
SigKey=DD46A68DB08C6B0086FDE4F198E0C656
AuthKey=31A43F9B548DB278EF1D0AF8E74BD5B016324526
DataFile=new.pkg
SigOffset=0
DataOffset=120
DataLen=-120

[4D53006E]
ID=[4D53006E]
Title=Forza Motorsport
SigKey=DD46A68DB08C6B0086FDE4F198E0C656
AuthKey=31A43F9B548DB278EF1D0AF8E74BD5B016324526
DataFile=UserProfile.xml
SigOffset=-20
DataOffset=0
DataLen=-20
SigType=NoRoam

[4D53006E_2]
ID=[4D53006E]
Title=Forza Motorsport Garage.bin/Garage.dat
SigKey=DD46A68DB08C6B0086FDE4F198E0C656
AuthKey=31A43F9B548DB278EF1D0AF8E74BD5B016324526
DataFile=Garage.bin
SigOffset=-20
DataOffset=0
DataLen=-20
SigType=NoRoam

If anyone can make the patch work on PAL Forza that will be great!

[brienj]

QUOTE(esgr_pt @ Jun 16 2005, 06:30 AM)

If anyone can make the patch work on PAL Forza that will be great!

Don't worry, either tonight, or tomorrow, you will be able to do any game.  

[brienj]

My latest program

Enjoy!  

[NarutoKun]

lol, just on time i just lost one years worth of Udata thx man.

[Heet]

[valrond]

Sorry for refloating this thread.

My problem is like many of the people that have a lot of Forza Motorsport done and need to transfer it to a new console. The thing is that I can't make it work in my 360. I have bought an XSATA, I transfer the files but I can't use my own savegame because of this "protection". Any hope of transfering ? I'm not going to start over Forza when I had over 40 hours done on my original xbox.

Thanks.