Conversation

Replying to
Just FYI, but at least with Apple’s implementation, the onboard SSD is cryptographically linked with the security coprocessor. Even if you could remove the SSD, there is nothing useful that can be done (unless you count erasing the drive as useful)
1
9
UFS/NVMe controller in the SoC is how most mobile devices work. Snapdragon has similar inline encryption/decryption support, but it's optional to use in the wrapped key mode where the OS can't access the keys. Even when it's not in wrapped key mode, keys are usually hw bound.
3
2
Nearly everyone other than Apple uses UFS rather than NVMe but they do have the storage controller as part of the SoC. I didn't mean that NVMe was common elsewhere but rather that it's normal to have it built-in to the SoC with inline encryption/decryption support for it.
1
2
You can see ext4 and f2fs have inline cryptography hardware support. The current generation implementation of filesystem-based encryption and the hardware support for it isn't available in the mainline kernel yet though. It tends to lag a couple years behind what's shipping.
1
I think ARM Chromebooks are usually using UFS SSD via an SoC storage controller now. I'd expect Windows ARM laptops are taking the same approach. NVMe is still better for a very high-end SSD so Qualcomm, etc. will probably integrate it the same way they do UFS for desktops.
1
They have more incentive than Apple to put it all in the SoC since it locks in sales. For example, no laptop using qualcomm.com/products/snapd is going to use Broadcom Wi-Fi because Snapdragon includes Atheros Wi-Fi/Bluetooth implemented as extra sandboxed processes on the baseband.