Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>The off-card model just seems like a complete architectural mismatch for the eSIM use case, since there is no single trustworthy entity. SAT applets are not presented to the eUICC vendor for bytecode verification, so the entire security model breaks down if verification doesn't happen on-card.

I thought the whole esim provisioning process required a chain of trust all the way to GSMA? Maybe the applet isn't verified by the eUICC vendor, but it's not like you can run whatever code either.



Seems like you actually could "run whatever code".

Apparently, GSMA recalled their universal eSIM test profiles. Prior to recall, those could be installed on ANY eSIM, and those profiles had applet updates enabled.

By installing a profile to eSIM and issuing your own update to it, you could run arbitrary applets.


If the set of actors that can deploy bytecode to eUICCs includes all operators issuing eSIMs worldwide, arguably it might as well be everybody.


Nah, it's only "everybody" when I'm on the list.

My major gripe with eSIM as a technology is that you can't just issue your own profiles to it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: