User Token Manager: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 17: Line 17:
| 0x25003 (Lv2)
| 0x25003 (Lv2)
| Decrypt User Token
| Decrypt User Token
| uint8[0xC50], 0xC50
| uint8_t out[0xC50], uint64_t size (0xC50)
|-
|-
| 0x25004 (Lv2)
| 0x25004 (Lv2)
Line 24: Line 24:
| 0x25005 (Lv2)
| 0x25005 (Lv2)
| Encrypt User Token
| Encrypt User Token
| uint8[0xC50], 0xC50
| uint8 out[0xC50], uint64_t size (0xC50)
|-
|-
|}
|}

Revision as of 16:21, 12 July 2014

0x25000 - User Token Manager

Packet ID Description Parameters
0x25001 Encrypt User Token
0x25002 Decrypt User Token
0x25003 (Lv2) Decrypt User Token uint8_t out[0xC50], uint64_t size (0xC50)
0x25004 (Lv2)
0x25005 (Lv2) Encrypt User Token uint8 out[0xC50], uint64_t size (0xC50)

User Token

  • Before User Token Manager encrypts a received user token it checks it's format.
  • User Tokens are processed by spu_utoken_processor.self
  • Before User Token is processed, User Token Manager reads IDPS by sending SS requests to Indi Info Manager (packet ids 0x17001 and 0x17002). Indi Info Manager runs in HV Process 5.

User Token Format

stuct user_token_attr
{
    uint32_t type;                                 /* 0x00000001, value != 0x00000001 means attribute list ends here */
    uint32_t size;                                 /* 8 + sizeof(data) */
    /* data follows here, size of data may be 0 */
}

struct user_token
{
    uint32_t magic;                                /* 0x73757400 = "sut\0" */
    uint32_t format_version;                       /* 0x00000001 */
    uint64_t size;
    uint8_t idps[16];
    uint64_t expire_date;
    uint64_t capability;
    union
    {
        stuct user_token_attr attrs[0];
        uint8_t dummy[3072];
    } attrs;
    /* 0xC30 */
    uint8_t digest[20];
}