2 ms·
I don't necessarily know how eSIMs or iSIMs are supposed to work, just throwing out some ideas here discussing how they could be implemented. Just because a de
by vel0city 4y ago
I don't necessarily know how eSIMs or iSIMs are supposed to work, just throwing out some ideas here discussing how they could be implemented.
Just because a device is on the same package or die doesn't mean all features need to be exposed to everything else on that package or die. Imagine if you just took the design for a regular SIM card, and then essentially just directly connected it on the package or on the die. Its still the same interface, but instead of it being a separate package connecting to pins on a board that connect to other pins on a board and then to the SoC its just all in the same plastic package. Then go from instead of wiring it in the plastic package, you're not wiring it on the die itself.
Now, of course, this obviously isn't how these things work, since they can load cryptographic material from things like QR codes and apps. While older SIMs were mostly read only (usually a small amount of user memory like address book stuff and what not) these newer eSIMs and iSIMs allow for provisioning in the field. This does bring some attack surface to them, but once again these kind of interfaces could be locked down. It doesn't necessarily need to share logic with the main CPU or have its memory in system RAM, it can still hold all its cryptographic secrets in its own private non-accessible memory and do its functions with its own logic designs. The provisioning step is still potentially attackable, but if designed right its secret storage and management can still be highly isolated to the main processors in the same way older SIMs were.