forked from PeterCxy/OpenEUICC
Peter Cai
c033ef5ba9
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.
33 lines
1.2 KiB
XML
33 lines
1.2 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<manifest xmlns:tools="http://schemas.android.com/tools"
|
|
xmlns:android="http://schemas.android.com/apk/res/android"
|
|
package="im.angry.openeuicc.common">
|
|
|
|
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
|
|
<uses-permission android:name="android.permission.INTERNET" />
|
|
|
|
<application>
|
|
<activity
|
|
android:name="im.angry.openeuicc.ui.SettingsActivity"
|
|
android:label="@string/pref_settings" />
|
|
|
|
<activity
|
|
android:name="im.angry.openeuicc.ui.NotificationsActivity"
|
|
android:label="@string/profile_notifications" />
|
|
|
|
<activity
|
|
android:name="im.angry.openeuicc.ui.DirectProfileDownloadActivity"
|
|
android:label="@string/profile_download"
|
|
android:theme="@style/Theme.AppCompat.Translucent" />
|
|
|
|
<activity
|
|
android:name="im.angry.openeuicc.ui.LogsActivity"
|
|
android:label="@string/pref_advanced_logs" />
|
|
|
|
<activity
|
|
android:name="com.journeyapps.barcodescanner.CaptureActivity"
|
|
android:screenOrientation="fullSensor"
|
|
tools:replace="screenOrientation" />
|
|
</application>
|
|
</manifest>
|