public/pysim
1
0
Fork 1
mirror of https://gitea.osmocom.org/sim-card/pysim.git synced 2026-05-02 02:16:26 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update patch set 3

Browse Source 
Patch Set 3:

(2 comments)

Patch-set: 3
This commit is contained in:
Gerrit User 1000028
2026-03-19 16:33:15 +00:00
committed by Gerrit Code Review
parent 2ec22b9241
commit b4467ddcfa
1 changed files with 36 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
177a45d2ae3c8df71a744fc145ed442fa53914a5
View File

@@ -17,6 +17,24 @@
"revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": false,
"key": {
"uuid": "4cf5210a_e1df87dc",
"filename": "docs/put_key-tutorial.rst",
"patchSetId": 2
},
"lineNbr": 80,
"author": {
"id": 1000028
},
"writtenOn": "2026-03-19T16:33:15Z",
"side": 1,
"message": "I have now reworked this. When I get https://euicc-manual.osmocom.org/docs/lpa/applet-id/ correctly then the purpose of the ISD-P is to be some kind of secure container of the profile. When it also is the \"on-card representative of the SM-DP+\", then the eSIM profile owner (MNO) probably has no influence here at all. This also may explain why it has no keys provisioned. As far as I understand now the ISD-P is not interesting at all in the scope of this tutorial. What we are interested in is the securityDomain that is specified in the eSIM profile.",
"parentUuid": "f00a2814_36ab91c0",
"revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": true,
"key": {
@@ -51,6 +69,24 @@
"revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": false,
"key": {
"uuid": "3eab4fe4_cf6a6d15",
"filename": "docs/put_key-tutorial.rst",
"patchSetId": 2
},
"lineNbr": 462,
"author": {
"id": 1000028
},
"writtenOn": "2026-03-19T16:33:15Z",
"side": 1,
"message": "I have checked this back. Remote Application Management over HTTP – Public Release v1.1.2, section 3.3.2 clearly says that the second key is a DEK key. So this is correct.",
"parentUuid": "e399c246_e2140b13",
"revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": true,
"key": {