Ernie Secure: Difference between revisions

From Vita Development Wiki
Jump to navigation Jump to search
No edit summary
Line 2: Line 2:


=== Part 1 ===
=== Part 1 ===
1. Generate an empty buffer <pre>30 00 00 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00</pre> and send it to Syscon.
# Generate an empty buffer <code>30 00 00 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00</code> and send it to Syscon.
2. Syscon returns header + 8 byte challenge.
# Syscon returns header + 8 byte challenge.


=== Part 2 ===
=== Part 2 ===
1. F00D composes a response that is <pre>30 02 00 0F</pre> header a <pre>01 00 00 00</pre> counter, 8 bytes of RNG value, 8 bytes copied from challenge, and 16 bytes of shared data. On 1.69, the shared data is <pre>C86B51FB019A207F32118E55462D5008</pre>
# F00D composes a data buffer that is 8 bytes of RNG value, 8 bytes copied from challenge, and 16 bytes of shared data. On 1.69, the shared data is <code>C86B51FB019A207F32118E55462D5008</code>
2. This data is encrypted using AES-128-CBC with all zero IV and a shared key. On 1.69, it is <pre>50E4C3A77264167C409C72A9B57A8609</pre>
# This data is encrypted using AES-128-CBC with all zero IV and a shared key. On 1.69, it is <code>50E4C3A77264167C409C72A9B57A8609</code>
# A header is prepended <code>30 02 00 0F 01 00 00 00</code> to the data and sent to Syscon


=== Part 3 ===
=== Part 3 ===
1. Gets a 0x28 byte response from Syscon with a 0x20 buffer.
# Gets a 0x28 byte response from Syscon with a 0x20 buffer.
2. Decrypt with AES-128-CBC with IV from part 2 (it is the last ciphertext generated, or the last 16 bytes of the ciphertext sent from F00D) and a shared key. On 1.69 it is <code>9E34087C48985B4B351A63572D9B481B</code>
# Decrypt with AES-128-CBC with IV from part 2 (it is the last ciphertext generated, or the last 16 bytes of the ciphertext sent from F00D) and a shared key. On 1.69 it is <code>9E34087C48985B4B351A63572D9B481B</code>
3. Check that first 8 byte matches unknown and next 8 byte matches the F00D nonce generated in part 1.
# Check that first 8 byte matches unknown and next 8 byte matches the F00D nonce generated in part 1.
4. Encrypt the same buffer back using a shared key for 16 bytes. On 1.69 it is <code>EBE3460D84A41754AC441368CF0200D8</code> and the IV will be the last 16 bytes from the encrypted input buffer.
# Encrypt the same buffer back using a shared key for 16 bytes. On 1.69 it is <code>EBE3460D84A41754AC441368CF0200D8</code> and the IV will be the last 16 bytes from the encrypted input buffer.
5. This is now the session key!
# This is now the session key!

Revision as of 16:31, 20 March 2018

Syscon 0xD0 four part key exchange

Part 1

  1. Generate an empty buffer 30 00 00 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 and send it to Syscon.
  2. Syscon returns header + 8 byte challenge.

Part 2

  1. F00D composes a data buffer that is 8 bytes of RNG value, 8 bytes copied from challenge, and 16 bytes of shared data. On 1.69, the shared data is C86B51FB019A207F32118E55462D5008
  2. This data is encrypted using AES-128-CBC with all zero IV and a shared key. On 1.69, it is 50E4C3A77264167C409C72A9B57A8609
  3. A header is prepended 30 02 00 0F 01 00 00 00 to the data and sent to Syscon

Part 3

  1. Gets a 0x28 byte response from Syscon with a 0x20 buffer.
  2. Decrypt with AES-128-CBC with IV from part 2 (it is the last ciphertext generated, or the last 16 bytes of the ciphertext sent from F00D) and a shared key. On 1.69 it is 9E34087C48985B4B351A63572D9B481B
  3. Check that first 8 byte matches unknown and next 8 byte matches the F00D nonce generated in part 1.
  4. Encrypt the same buffer back using a shared key for 16 bytes. On 1.69 it is EBE3460D84A41754AC441368CF0200D8 and the IV will be the last 16 bytes from the encrypted input buffer.
  5. This is now the session key!