forked from PeterCxy/OpenEUICC
Unfortunately, because there is no way to access the certificate itself from the eUICC, we have to hard-code known & supported certificates still. However, this approach makes sure that only those certificates listed by the eUICC are trusted during their SM-DP+ sessions. Were these added directly as part of the Android security config, then all certificates would be blindly trusted for all SM-DP+ sessions (and even normal TLS connections if the app were to make them). As a result we can now trust more known certificates, including GSMA Test CIs. These are hard-coded as a hash map. |
||
---|---|---|
.. | ||
src | ||
.gitignore | ||
build.gradle.kts | ||
consumer-rules.pro | ||
proguard-rules.pro |