Changes

The Starbuck's boot chain ([[boot0]] and [[boot1]]) only boots signed code in the form of an ancast image as well. On the ARM side, the IOS-MCP module is responsible for launching [[cafe2wii]] and relaunching IOSU (warm boot). IOS-MCP loads ARM ancast images into MEM1 (0x01000000), verifies and decrypts them before executing with full privileges (all memory protection is disabled and must be re-enabled by the binary itself).

The Starbuck's boot chain ([[boot0]] and [[boot1]]) only boots signed code in the form of an ancast image as well. On the ARM side, the IOS-MCP module is responsible for launching [[cafe2wii]] and relaunching IOSU (warm boot). IOS-MCP loads ARM ancast images into MEM1 (0x01000000), verifies and decrypts them before executing with full privileges (all memory protection is disabled and must be re-enabled by the binary itself).

Ancast images consist of a signature and related information, known as the ancast header, and the AES-encrypted code, known as the cipher text. ARM and PPC ancast images both use AES-128-CBC for encryption, but differ in signature algorithms. For this reason, their headers are also different.

Ancast images consist of a signature and related information, known as the ancast header, and the AES-encrypted code, known as the ancast body. ARM and PPC ancast images both use AES-128-CBC for encryption, but differ in signature algorithms. For this reason, their headers are also different.

"Ancast" is an unofficial acronym for "The princess is in <u>an</u>other <u>cast</u>le", which is a pun introduced during fail0verflow's initial hacking efforts. It doesn't transmit any actual meaning besides that.

"Ancast" is an unofficial acronym for "The princess is in <u>an</u>other <u>cast</u>le", which is a pun introduced during fail0verflow's initial hacking efforts. It doesn't transmit any actual meaning besides that.