2 ms·
This is an honest question. Why is it not possible to run decryption directly against the data?
by wodenokoto 11y ago
This is an honest question. Why is it not possible to run decryption directly against the data?
- tzs 11y agoThere are two main chips involved here. One is the NAND flash chip that contains the encrypted user data. The other is the CPU chip, which contains the CPU but also contains other functional units. In particular, it contains a cryptography processor. When the cryptography processor is manufactured, a random number (256 bits long, I believe) is built into the hardware. This random number is different for each chip, and it is not recorded anywhere. One of the functions provided by the cryptography processor is generating a 256 bit encryption key from a shorter passcode. That function makes use of that built-in unique per-chip number. Let's call this 256 bit key the "master key". That master key is used to encrypt the NAND flash. (Actually, I think there is one more level in there. Each file is encrypted with a random key, and that file's key is encrypted with the master key and stored in the file metadata). When you try a brute force attack directly against the encrypted NAND flash it is that 256 bit master key that you have to brute force. Brute forcing a 256 bit AES key is far beyond the capabilities of anything in existence, no matter how big their budget and how many people they can throw at the problem. The only thing feasible to brute force is the passcode, but unless you can take the CPU apart and examine it in sufficient detail to determine that chip's unique number, you have to use the cryptographic coprocessor from that specific phone to do the passcode to master key derivation for each try.