View Full Version : XBE Signing
lllsondowlll
07-08-2009, 05:10 AM
Dumb question but I found an XBE signer, will the signer run modified Xbe's on a retail console with modified firmware or does it just fix the signiture in a way that isn't recognized by retails? Just wondering because I don't think MS private key was leaked so this seems like its used for something else, beyond that I can't figure out what :-/
http://forums.xbox-scene.com/index.php?showtopic=165718
l_oliveira
07-08-2009, 10:47 AM
Why would you need to sign a XBE properly if you can just override the console kernel and use a hacked one ?
(This is about the original XBOX, right ?)
And (fake)signing stuff is usually related to softmodding. So one of the purposes of such tools are prepare exploit files for use.
And yes I don't think the MS private key was ever leaked.
lllsondowlll
07-08-2009, 12:53 PM
Because I am working on a project and I stumbled across this and it would be useful if the XBE files that are signed would be able to run from a retail console with a flashed drive so will this work or not?
... This one was for old exploits where the private key was changed, not that they "hacked" the private microsoft one.
Kishan
07-08-2009, 07:57 PM
How many people at microsoft have access to the private key. someone told me only the executives at the xbox operation centre have access to it
How many people at microsoft have access to the private key. someone told me only the executives at the xbox operation centre have access to it
I honestly doubt anyone even has a signer aplication just lying on their desktop, I believe there is a server that needs serious credentials in order to process and sign an xbe/xex.
Kishan
07-08-2009, 08:11 PM
now....... lets brickforce attack that server. lol
now....... lets brickforce attack that server. lol
Kishan you really know absolutely nothing about xbox development, refrain from making useless posts/topics like the 7 you've made this past morning and keep them to one topic. Not to be an ass but some things your saying are just plain ingnorant statements
Why would the server have a public acsses, who would need it outside of MS?
Kishan you really know absolutely nothing about xbox development, refrain from making useless posts/topics like the 7 you've made this past morning and keep them to one topic. Not to be an ass but some things your saying are just plain ingnorant statements
Why would the server have a public acsses, who would need it outside of MS?
Indeed. Even if it was MS would notice the sudden traffic jump from the internet and cut us off before anyone could get anywhere. Then come the G-Men with warrants and you get a human booster shot from a guy named Molly.
Think before you speak Kishan.
Kishan
07-09-2009, 01:15 AM
Indeed. Even if it was MS would notice the sudden traffic jump from the internet and cut us off before anyone could get anywhere. Then come the G-Men with warrants and you get a human booster shot from a guy named Molly.
Think before you speak Kishan.
sorry. i was being ignorant and i promise to try and make usefull contributions next time.
lllsondowlll
07-11-2009, 10:39 PM
... This one was for old exploits where the private key was changed, not that they "hacked" the private microsoft one.
Can an XBE be signed and run on an retail Xbox1/360 with a modified drive in its current state? I have little insight on why there is a "XBE Signer" so any information is helpful.
Can an XBE be signed and run on an retail Xbox1/360 with a modified drive in its current state? I have little insight on why there is a "XBE Signer" so any information is helpful.
There is an xbe signer because older xbox 1 exploits, required the xbes to still be signed, just not with the Microsoft private key. Newer ones allowed unsigned xbe.
If I had evox installed back in the old old days, all my apps had to be signed with some special key, like a dev. Thats why you see all these xbe signers.
lllsondowlll
07-13-2009, 12:27 AM
Thanks for clearing that up bro.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.