PUP

PUP (Playstation Update Package) files are update archives for the PS3, PSVita and PS4.

= PUP Structure =

A good resource on the PUP structure can be found HERE.

= Update .PKG files =

Most of the files in the update PUP are .pkg files, a sort of Certified File.

Each component of the update is broken up into multiple parts, then optionally compressed, and finally encrypted into the PKG.

Package Header
Right after the Certified File header (usually at offset 0x400) is the update package header that provides information for piecing the component back together. The contents of this header is as follows:

Flags
There are flags that are set in the package header. Some potential ones are listed here.

Type ID
The type id determines which decryption routine to use in SceSblSsUpdateMgr. There is a truth table to determine which id can be handled by which decryption function. To see how this table is used, check out the example code for decrypting packages.

Type ID (Identifier)
The type ID is also used to identify the component of the update.

= SCEWM =

SCEWM is a file embedded in the PUP to serve as a watermark.

PUP Watermark is present since at least FW 0.931.010. It was not present on FW 0.902.000. Nevertheless, on FW 0.931.010 OS the PUP watermark is never verified.

The SCEWM file is composed of 2 parts:
 * SCEWM header: size 0x20 bytes.
 * SCEWM body: size = file_size(usually 0x1000) - header_size(0x20). This part is encrypted.

Header
This is a watermark for PUPs. For development PUPs, the Issue ID is unique to the company/organization the PUP is issued to.

The message length for prototype/retail PUP is almost always 0x5A, see below why.

Body
The body is encrypted using AES128CBC with key and iv from update_service_sm.self.

After decryption, the body is composed of 3 parts:
 * 0x100 bytes: RSA2048 signature of SHA256 of the PUP Header Digest. It is verified with SCEWM RSA public key. The PUP Header is independant of the watermark and so is the RSA signature.
 * 0xDE0 bytes: plaintext ASCII message (unique message per DevNet issue ID or build time).
 * 0x100 bytes: RSA2048 signature of SHA256 of 0xF00 bytes (SCEWM header + decrypted PUP Header Digest signature + decrypted message). It is verified with SCEWM RSA public key.

PUP Header Digest RSA Signature
It is RSA2048 of SHA256 of the PUP Header Digest. It is verified with SCEWM RSA public key.

Default Watermark Message
For PUP not bound to a developer, not downloaded on DevNet, such as prototype and retail PUP, the watermark has a default message.

0.931-3.73: desc: default watermark id: build_team timestamp: YYYYMMDD_HHmmSS_JST host: build_machine

DevNet Watermark Message
The message is generated on developer's demand by DevNet server, written to the PUP, then the PUP download starts. The message syntax has changed with DevNet revisions.

The message is totally independant of the PUP. The same PUP (for example PSVita FW 0.945 PUP) downloaded from DevNet in 2011 and in 2018 has different message syntax.

Here 'x' represents an actual character, which I hide for confidentiality.

Old message (2011-02)
User id:xxxxxx Org name:xxxxxxxxxxxxxx Company name:xxxxxxxxxxxxxxxxxxxxxxxxxxxx Date PUP downloaded:YYYY-MM-DD HH:mm Host IP address:xxx.xxx.xxx.xxx
 * 1) PUP watermark data that contain DevNet user id, org name, company name, date of PUP downloaded and host IP address

Recent message (2018-04)
PUP serial number:xxxxxxxx
 * 1) PUP watermark data contain a serial_number that associates with the user who download this PUP
 * 2) Provide the serial number below to the DevNet development team to get user and org details.

SCEWM RSA Signature
It is RSA2048 of SHA256 of 0xF00 bytes: the SCEWM header + the decrypted SCEWM body. It is verified with SCEWM RSA public key.

Security
When comparing the same PUP signed for two different issue IDs, we can notice only 2 differences:
 * sometimes the message length in SCEWM header
 * the SCEWM encrypted unique data: the blocks of the message that differ and the RSA signature of the watermark

= SCEAS =

This file contains Additional Signature(s) (A.S.) necessary for validation of the PUP.

It was added on FW 0.996, probably for security reasons. This file is missing inside the Prototype DevKit PUP 0.945.040 (and all the pre-0.996 PUPs).

The SCEAS file is composed of 2 parts:
 * SCEAS header: size 0x20 bytes.
 * SCEAS body: size = file_size(usually 0x1000) - header_size(0x20). This part is encrypted.

Body
The body is encrypted using AES128CBC with key and iv from update_service_sm.self.

After decryption, the body is composed of 3 parts:
 * 0x100 bytes: RSA2048 signature of something unknown (to reverse). It is verified with SCEAS RSA public key.
 * 0x1E0 bytes: zeroes, maybe area for more than one signature, or just padding for decryption.
 * 0x100 bytes: RSA2048 signature of SHA256 of ?0x300 bytes (SCEAS header + decrypted unknown signature)?. It is verified with SCEAS RSA public key.