It’s extractor/packer for official PS3 firmware update files.

1. added hmac key support;
2. fixed filename support for latest firmwares;
3. added support for incremental ps3 update files (PS3PATCH.PUP);
4. removed xml configuration (now configuration is saved in binary file config.bin);
Due to released decryption keys for selfs, today I’ve found HMAC key for firmware signing. Key is located in decrypted software_update_plugin.prx at 0x602E0 (I used dumps from 3.15 firmware). I’ve found it by bruteforce (thanks to full signing algo source from team0verflow).
It’s funny, that while I was preparing my sources with sign key, Kakaroto already released the key
.
Here is source and precompiled windows version.
For linux, you can build it with CodeBlocks IDE, project file included, but you’ll need libboost_filesystem headers and libraries installed.
http://superg.org.ua/files/ps3/gpup/gpup-1.00.tar.bz2
http://superg.org.ua/files/ps3/gpup/gpup-1.00_win.7z
gpup is currently fully finished, I performed some extract-pack tests of official firmwares, and it able to recombine all firmwares 1:1.
Bugreports are welcome.




01-03-2011
09:17 PM
Downloading now for a test run
01-03-2011
09:31 PM
sorry im a noob....but whats this for? it basically allows for packaging of cfw right?....atleast thats what i understand from it?...once again sorry i suck and im a noob
01-03-2011
10:06 PM
Can you upload this compiled? thank you and sorry if my english is bad
01-03-2011
11:02 PM
thanks a lot for the work putting this together. I can not believe how fast these tools are coming out.
01-04-2011
12:58 AM
I keep getting error on creating xxxx.PUP could not read config.bin.
EDIT,
NM got it to work, just sleepy.
Thanks for this.
01-04-2011
05:34 AM
how safe is it to mix up different updates?
for example using all files of 3.41 and just replacing version.txt (and other related files) from 3.55 to trick the ps3 and make it look like a 3.55 update file?
or how about mixing up debug with retail updates?
01-04-2011
06:40 AM
01-04-2011
07:00 AM
The 3.41 => 3.55 might not brick anything BUT it seems 3.55 has different sys calls than the 3.41 has. Code linked against those new sys calls might not work.
Debug => Retail... how about some Red Screen Of Epic Fail ?
Debug Units might be hardware different than Retail ones. Mixing their FW could be possible... but will end up in brick if you dont know exactly which part of the code you can safely run on Retail...