Post: New idea on how to sign package
09-27-2010, 03:05 AM #1
Norman
NORMAN
(adsbygoogle = window.adsbygoogle || []).push({}); Alright now this very well may work, or i may go down in my own flames, dying a slow death. but if we take a signed package from sony, and unpack it with the latest SDK, then we pack it with the SDK, then it wont be signed, so we will have 2 pkg files, one signed, one not. both containing the same data with the same stuff, just one pkg got signed by sony, and one didnt. now i know this next part will be the most noobish thing to say, but we could put them on a hex editor, then view the differences. if im correct the only difference we should see is the signature.
plz dont flame if im stupid. i just want to help by pitching ideas out here.:whistle:
(adsbygoogle = window.adsbygoogle || []).push({});
09-27-2010, 03:06 AM #2
Ritztro
I am a Game Developer
Good idea.. I will try it eventually lol

Edit: Someone will probably be like. NO it wont work!
09-27-2010, 03:17 AM #3
shiver
chaos personified
YOU STUPID SON OF A B******!!!!!!!!!!

ok jokes Happy

Welcome to NGU!!!

The following 2 users say thank you to shiver for this useful post:

Alfa, NiCiUFF
09-27-2010, 03:20 AM #4
Norman
NORMAN
yeah i know. i would love to test on my own. but i dont have what a hacker needs, Linux!!!!!!!!!!!/facepalm
09-27-2010, 03:21 AM #5
NO it wont work!
^ Had to do it.
My guess is that the package may still be signed after being repacked (if you don't change anything).
09-27-2010, 04:11 AM #6
Norman
NORMAN
thanks for the warm welcome guys. ^^^yeah i know i thought about that too. if we dont change any thing then why wouldnt it be signed right? but hey we dont know how they sign stuff right? Eek

---------- Post added at 11:11 PM ---------- Previous post was at 10:27 PM ----------

because retail packages can not be decrypted without the aid of a PS3, and the only way to re-encrypt them would be to use development keys (since, we lack retail ones) - so on compare they would be very, different. so it would not work

Furthermore, there is still a matter of the encrypted executable (the .self, usually the EBOOT.BIN) - which is another entire issue. so gosh dangit sony
09-27-2010, 04:58 AM #7
Alfa
Banned
i put a little thought into this and wondered about this.. how the **** are you gonna decompress a signed pkg...
09-27-2010, 05:40 AM #8
hunter12
Retired, done with gaming
Originally posted by Alfa
i put a little thought into this and wondered about this.. how the **** are you gonna decompress a signed pkg...


magic you noob /facepalm
jk
09-27-2010, 06:32 AM #9
Xcellerator
You talkin to me?
I have looked into this...
You cannot decrypt Signed (Authorised) PKGs. If you install it on the PS3, and then try to repack it by copying it over, you still cannot pack the file. When Sony authorise a PKG, they also authorise the EBOOT.BIN individually so it cannot be packed into a PKG, and cannot be converted to a ELF... :/
09-27-2010, 07:06 AM #10
hunter12
Retired, done with gaming
Originally posted by Xcellerator View Post
I have looked into this...
You cannot decrypt Signed (Authorised) PKGs. If you install it on the PS3, and then try to repack it by copying it over, you still cannot pack the file. When Sony authorise a PKG, they also authorise the EBOOT.BIN individually so it cannot be packed into a PKG, and cannot be converted to a ELF... :/


Decrypting the EBOOT is easy just do a simple memory dump..
also known as LV2 dump = D

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo