5 ms·
Do you know why is this a closed shop? Is there a legal reason or whichever corporation controls it ensured that they have a monopoly? Is there a way to open th
by varispeed 5y ago
Do you know why is this a closed shop? Is there a legal reason or whichever corporation controls it ensured that they have a monopoly? Is there a way to open this up?
- g_p 5y agoFrom memory, I believe GSMA (the industry association that helps to keep mobile technology dominated by carriers that hold exclusively licensed spectrum, if you're cynical) require everyone who provides eSim to have been security audited. They can then get access to a trusted certificate that will be able to sign the handshake to the embedded security module (eSim). It's complex, but remember that in the traditional world view of mobile, the carrier "owns" the SIM, and the handset, and the network itself. When the carrier can't control the SIM in its entirety, you need to have someone brokering the relationship here between everyone - otherwise a carrier coming onto a device may lack confidence the device isn't compromised by the previous network that served it. Some information that might help you start look around the topic - https://pages.arm.com/rs/312-SAX-488/images/GSMA_eSIM_Certification_Guide%20%281%29.pdf https://pages.arm.com/rs/312-SAX-488/images/GSMA_eSIM_Certif...
- lxgr 5y agoeSIM implementations need to be closed because they are considered a secure execution environment for loading eSIM profiles (in that it should not be possible to extract the keys contained in a profile). I'm not actually sure if there is a good reason for the eSIM profile server (called SM-DP+ in the language of the specs) to be part of the same trusted computing base; maybe defense in depth against a malicious profile/SAT applet trying to access the data of others on the same eSIM?