Post: BLACKBOX FTP signed WITH PRIVATE KEYS
Options
12-31-2010, 05:13 PM
#1
NgUBiGBiRD
Haxor!
01-01-2011, 08:00 PM
#21
bonbonbon
dead babies in a tree
Originally posted by ihaxgames
Are you saying signing retail PKGs would be useless, or the PKGs and the executables? I already know how we can install files when it does work, however I'm assuming that you know how we can do that without the "Install Package Files Option" i might not understand what you were trying to say
You mean with PS3 proxy? That's how it would probably be done
The following user thanked hunter12 for this useful post:
01-02-2011, 11:52 PM
#27
eStyle_Chupa
Brute
This is what I think we should be working on (found by me, if there was anything to be found XD):
Tomorrow, I will look into this more closely, but my research got me into this:
Once we unpack the .PKG from the FTP server, we get a PARAM.SFO, a .PNG and a folder named USRDIR with a EBOOT.BIN. With one of the released PS3 GUI TOOLBOX versions, we could unpack this EBOOT.BIN and get a EBOOT.SELF. This .SELF is of grave importance for signing keys, I think. We have to sign them SOMEHOW into the .SELF to make them look like Sony's own application.
After we've done that, we have to reverse the entire process: repack the .SELF into the EBOOT.BIN, replace the modified EBOOT.BIN with the old EBOOT.BIN, repack the .PKG and upload in onto the PS3.
This would most likely work, I think. Main problem: where to sign the keys into the .SELF?
Tomorrow, I will look into this more closely, but my research got me into this:
Once we unpack the .PKG from the FTP server, we get a PARAM.SFO, a .PNG and a folder named USRDIR with a EBOOT.BIN. With one of the released PS3 GUI TOOLBOX versions, we could unpack this EBOOT.BIN and get a EBOOT.SELF. This .SELF is of grave importance for signing keys, I think. We have to sign them SOMEHOW into the .SELF to make them look like Sony's own application.
After we've done that, we have to reverse the entire process: repack the .SELF into the EBOOT.BIN, replace the modified EBOOT.BIN with the old EBOOT.BIN, repack the .PKG and upload in onto the PS3.
This would most likely work, I think. Main problem: where to sign the keys into the .SELF?
01-03-2011, 08:20 AM
#28
bonbonbon
dead babies in a tree
Originally posted by Chupa
This is what I think we should be working on (found by me, if there was anything to be found XD):
Tomorrow, I will look into this more closely, but my research got me into this:
Once we unpack the .PKG from the FTP server, we get a PARAM.SFO, a .PNG and a folder named USRDIR with a EBOOT.BIN. With one of the released PS3 GUI TOOLBOX versions, we could unpack this EBOOT.BIN and get a EBOOT.SELF. This .SELF is of grave importance for signing keys, I think. We have to sign them SOMEHOW into the .SELF to make them look like Sony's own application.
After we've done that, we have to reverse the entire process: repack the .SELF into the EBOOT.BIN, replace the modified EBOOT.BIN with the old EBOOT.BIN, repack the .PKG and upload in onto the PS3.
This would most likely work, I think. Main problem: where to sign the keys into the .SELF?
Tomorrow, I will look into this more closely, but my research got me into this:
Once we unpack the .PKG from the FTP server, we get a PARAM.SFO, a .PNG and a folder named USRDIR with a EBOOT.BIN. With one of the released PS3 GUI TOOLBOX versions, we could unpack this EBOOT.BIN and get a EBOOT.SELF. This .SELF is of grave importance for signing keys, I think. We have to sign them SOMEHOW into the .SELF to make them look like Sony's own application.
After we've done that, we have to reverse the entire process: repack the .SELF into the EBOOT.BIN, replace the modified EBOOT.BIN with the old EBOOT.BIN, repack the .PKG and upload in onto the PS3.
This would most likely work, I think. Main problem: where to sign the keys into the .SELF?
signiture is FINAL step i believe. i could also be wrong:bro:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
