August 2026 - gerrit-log - lists.osmocom.org

[M] Change in simtrace2[master]: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA
by lynxis lazus 12 Aug '26

12 Aug '26

Attention is currently required from: dexter, laforge. lynxis lazus has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email ) Change subject: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA ...................................................................... Patch Set 8: (2 comments) File host/lib/apdu_dispatch.c: https://gerrit.osmocom.org/c/simtrace2/+/43185/comment/4bf80757_c47bf41a?us… : PS3, Line 120: ac->hdr.cla & 0x80 && /* check for GP */ > In GlobalPlatform Card Specification, section 11.3.2 they list more possible CLA bytes. […] I don't know what I should do here. Should I drop the requirement for Global Platform and treat all previous case 2 as a case 2?Or keep the code as it? File host/tests/apdu_dispatch/apdu_dispatch_test.c: https://gerrit.osmocom.org/c/simtrace2/+/43185/comment/83cfd253_ebb0fbcf?us… : PS3, Line 70: OSMO_ASSERT(rc == APDU_ACT_TX_CAPDU_TO_CARD); > I wonder if it would make sense to inspect the contents of ac and prev_ac after osmo_apdu_segment_in […] I've added a check on apdu_case. -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 Gerrit-Change-Number: 43185 Gerrit-PatchSet: 8 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-Comment-Date: Wed, 12 Aug 2026 13:31:54 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>

1 0

[M] Change in simtrace2[master]: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA
by lynxis lazus 12 Aug '26

12 Aug '26

Attention is currently required from: laforge, lynxis lazus. Hello Jenkins Builder, dexter, laforge, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email to look at the new patch set (#8). Change subject: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA ...................................................................... Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA osmo_apdu_segment_in() doesn't have the context of the previous APDU, for nearly all calls this is fine, except for GP GET DATA, which can be a case 2 or case 4 APDU. GP GET DATA defines the Le field as 0x00 which is used by osmo_apdu_segment_in to detect if it is a case 2 or case 4. But if the card responded to a case 2 GP GET DATA with Le = 0 with a SW 6cXX, the previous GP GET DATA case 2 must be resent with a Le field XX, which got misinterpreted by the osmo_apdu_segment_in() as a case 4 APDU instead of a case 2. Introduce osmo_apdu_segment_in2() containing the previous APDU as context. Modem <-> Card 81cadf2000 -> <- 6c0b 81cadf200b -> -- Simtrace waits for more data because it wrongly decodes it as APDU case 4 instead of case 2. Related: SYS#8147 Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 --- M TODO-RELEASE M host/Makefile.am M host/configure.ac M host/include/osmocom/simtrace2/apdu_dispatch.h M host/lib/apdu_dispatch.c A host/tests/Makefile.am A host/tests/apdu_dispatch/Makefile.am A host/tests/apdu_dispatch/apdu_dispatch_test.c A host/tests/apdu_dispatch/apdu_dispatch_test.ok A host/tests/testsuite.at 10 files changed, 199 insertions(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/simtrace2 refs/changes/85/43185/8 -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newpatchset Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 Gerrit-Change-Number: 43185 Gerrit-PatchSet: 8 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>

1 0

[M] Change in simtrace2[master]: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA
by dexter 12 Aug '26

12 Aug '26

Attention is currently required from: laforge, lynxis lazus. dexter has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email ) Change subject: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA ...................................................................... Patch Set 6: Code-Review+1 (2 comments) Patchset: PS5: I think I understand it better now. So when we receive the 6cXX from the card. We replay the header, but unless we do not memorize the case from the original transmission the following code assumes that the replay transmission is a case 4 and it indefinitely waits for more data from the terminal. So memorizing the case from the original transmission is how we get around this. Commit Message: https://gerrit.osmocom.org/c/simtrace2/+/43185/comment/a46a16be_70238c09?us… : PS3, Line 17: instead of a case 2 with Le != 0. > I am having difficulties to understand this description. […] Done -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 Gerrit-Change-Number: 43185 Gerrit-PatchSet: 6 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Comment-Date: Wed, 12 Aug 2026 13:29:55 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>

1 0

[M] Change in simtrace2[master]: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA
by lynxis lazus 12 Aug '26

12 Aug '26

Attention is currently required from: dexter, laforge. Hello Jenkins Builder, dexter, laforge, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email to look at the new patch set (#7). The following approvals got outdated and were removed: Verified+1 by Jenkins Builder Change subject: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA ...................................................................... Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA osmo_apdu_segment_in() doesn't have the context of the previous APDU, for nearly all calls this is fine, except for GP GET DATA, which can be a case 2 or case 4 APDU. GP GET DATA defines the Le field as 0x00 which is used by osmo_apdu_segment_in to detect if it is a case 2 or case 4. But if the card responded to a case 2 GP GET DATA with Le = 0 with a SW 6cXX, the previous GP GET DATA case 2 must be resent with a Le field XX, which got misinterpreted by the osmo_apdu_segment_in() as a case 4 APDU instead of a case 2. Introduce osmo_apdu_segment_in2() containing the previous APDU as context. Modem <-> Card 81cadf2000 -> <- 6c0b 81cadf200b -> -- Simtrace waits for more data instead sends the APUD case 2 to the card. Related: SYS#8147 Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 --- M TODO-RELEASE M host/Makefile.am M host/configure.ac M host/include/osmocom/simtrace2/apdu_dispatch.h M host/lib/apdu_dispatch.c A host/tests/Makefile.am A host/tests/apdu_dispatch/Makefile.am A host/tests/apdu_dispatch/apdu_dispatch_test.c A host/tests/apdu_dispatch/apdu_dispatch_test.ok A host/tests/testsuite.at 10 files changed, 199 insertions(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/simtrace2 refs/changes/85/43185/7 -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newpatchset Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 Gerrit-Change-Number: 43185 Gerrit-PatchSet: 7 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: dexter <pmaier(a)sysmocom.de>

1 0

[M] Change in simtrace2[master]: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA
by lynxis lazus 12 Aug '26

12 Aug '26

Attention is currently required from: dexter, laforge. lynxis lazus has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email ) Change subject: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA ...................................................................... Patch Set 6: (3 comments) File host/tests/apdu_dispatch/apdu_dispatch_test.c: https://gerrit.osmocom.org/c/simtrace2/+/43185/comment/70138950_0b847ed7?us… : PS3, Line 18: memset(&prev_ac, 0, sizeof(prev_ac)); \ > prev_ac only appears in the memset and nowhere else, is this line needed in this macro? Done https://gerrit.osmocom.org/c/simtrace2/+/43185/comment/e99c3e3f_c6e62f86?us… : PS3, Line 22: printf("%d (actual) != %d (intended)\n", rc, exp_rc);\ > I think (expected) is more accurate. The variable is also called "exp_rc". Done https://gerrit.osmocom.org/c/simtrace2/+/43185/comment/0209f618_d0b3ca17?us… : PS3, Line 55: rc = osmo_apdu_segment_in2(&ac, &prev_ac, get_data_c2_ca, ARRAY_SIZE(get_data_c2_ca), 1); > The last parameter of osmo_apdu_segment_in2 is a bool. […] Done -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 Gerrit-Change-Number: 43185 Gerrit-PatchSet: 6 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-Comment-Date: Wed, 12 Aug 2026 13:23:04 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>

1 0

[M] Change in simtrace2[master]: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA
by lynxis lazus 12 Aug '26

12 Aug '26

Attention is currently required from: dexter, laforge, lynxis lazus. Hello Jenkins Builder, dexter, laforge, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email to look at the new patch set (#6). The following approvals got outdated and were removed: Verified+1 by Jenkins Builder Change subject: Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA ...................................................................... Add osmo_apdu_segment_in2() to ensure correct parsing of GP GET DATA osmo_apdu_segment_in() doesn't have the context of the previous APDU, for nearly all calls this is fine, except for GP GET DATA, which can be a case 2 or case 4 APDU. GP GET DATA defines the Le field as 0x00 which is used by osmo_apdu_segment_in to detect if it is a case 2 or case 4. But if the card responded to a case 2 GP GET DATA with Le = 0 with a SW 6cXX, the previous GP GET DATA case 2 must be resent with a Le field XX, which got misinterpreted by the osmo_apdu_segment_in() as a case 4 APDU instead of a case 2. Introduce osmo_apdu_segment_in2() containing the previous APDU as context. Modem <-> Card 81cadf2000 -> <- 6c0b 81cadf200b -> -- Simtrace waits for more data instead sends the APUD case 2 to the card. Related: SYS#8147 Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 --- M TODO-RELEASE M host/Makefile.am M host/configure.ac M host/include/osmocom/simtrace2/apdu_dispatch.h M host/lib/apdu_dispatch.c A host/tests/Makefile.am A host/tests/apdu_dispatch/Makefile.am A host/tests/apdu_dispatch/apdu_dispatch_test.c A host/tests/apdu_dispatch/apdu_dispatch_test.ok A host/tests/testsuite.at 10 files changed, 195 insertions(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/simtrace2 refs/changes/85/43185/6 -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43185?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newpatchset Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: Ie238662e7e6a10dd4283ede0c8d8d73bc375c247 Gerrit-Change-Number: 43185 Gerrit-PatchSet: 6 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Attention: dexter <pmaier(a)sysmocom.de>

1 0

[S] Change in onomondo-eim[master]: rest_api_resource/response_schema: add spec ref for ICCID
by dexter 12 Aug '26

12 Aug '26

dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43207?usp=email ) Change subject: rest_api_resource/response_schema: add spec ref for ICCID ...................................................................... rest_api_resource/response_schema: add spec ref for ICCID This eIM accepts the ICCID in it raw form (as found in EF.ICCID). Let's add a spec ref so users can look up the exact format quicker. Related: SYS#8100 Change-Id: Idf6f29386b9b6df9255e10d0dd2909c7297709e4 --- M contrib/rest_api_resource_schema.json M contrib/rest_api_response_schema.json 2 files changed, 5 insertions(+), 5 deletions(-) git pull ssh://gerrit.osmocom.org:29418/onomondo-eim refs/changes/07/43207/1 diff --git a/contrib/rest_api_resource_schema.json b/contrib/rest_api_resource_schema.json index 2e0d330..0a7764b 100644 --- a/contrib/rest_api_resource_schema.json +++ b/contrib/rest_api_resource_schema.json @@ -42,7 +42,7 @@ "type": "object", "properties": { "iccid": { - "description": "ICCID of the profile. (ICCID in nibble-swapped raw format)", + "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", "pattern": "^[0-9,A-F]{2,32}$" }, @@ -62,7 +62,7 @@ "type": "object", "properties": { "iccid": { - "description": "ICCID of the profile. (ICCID in nibble-swapped raw format)", + "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", "pattern": "^[0-9,A-F]{2,32}$" } @@ -104,7 +104,7 @@ }, { "iccid": { - "description": "ICCID of the profile. (ICCID in nibble-swapped raw format)", + "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", "pattern": "^[0-9,A-F]{2,32}$" } diff --git a/contrib/rest_api_response_schema.json b/contrib/rest_api_response_schema.json index 7ec2735..867baa4 100644 --- a/contrib/rest_api_response_schema.json +++ b/contrib/rest_api_response_schema.json @@ -93,7 +93,7 @@ "type": "object", "properties": { "iccid": { - "description": "ICCID of the profile. (ICCID in nibble-swapped raw format)", + "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", "pattern": "^[0-9,A-F]{2,32}$" }, @@ -402,7 +402,7 @@ ] }, "iccid": { - "description": "ICCID of the profile. (ICCID in nibble-swapped raw format)", + "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", "pattern": "^[0-9,A-F]{2,32}$" } -- To view, visit https://gerrit.osmocom.org/c/onomondo-eim/+/43207?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: onomondo-eim Gerrit-Branch: master Gerrit-Change-Id: Idf6f29386b9b6df9255e10d0dd2909c7297709e4 Gerrit-Change-Number: 43207 Gerrit-PatchSet: 1 Gerrit-Owner: dexter <pmaier(a)sysmocom.de>

1 0

[S] Change in onomondo-eim[master]: config: update sys.dev.config
by dexter 12 Aug '26

12 Aug '26

dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43209?usp=email ) Change subject: config: update sys.dev.config ...................................................................... config: update sys.dev.config The config file sys.dev.config still has outdated SSL certificate paths in it. Let's fix it up so that it has the correct paths. Related: SYS#8100 Change-Id: I4d8c91d787e6932fbcab7f0dcbdea620894a61c2 --- M config/sys.dev.config 1 file changed, 8 insertions(+), 8 deletions(-) git pull ssh://gerrit.osmocom.org:29418/onomondo-eim refs/changes/09/43209/1 diff --git a/config/sys.dev.config b/config/sys.dev.config index 4072af3..a6eb22a 100644 --- a/config/sys.dev.config +++ b/config/sys.dev.config @@ -3,24 +3,24 @@ {esipa_ip, {127, 0, 0, 1}}, {esipa_port, 8000}, {esipa_ssl_disable, true}, - {esipa_ssl_cert, "config/sample_ssl_cert.crt"}, - {esipa_ssl_key, "config/sample_ssl_cert.key"}, + {esipa_ssl_cert, "sample_ssl_cert.crt"}, + {esipa_ssl_key, "sample_ssl_cert.key"}, {rest_ip, {127, 0, 0, 1}}, {rest_port, 8080}, {eim_id, "eIM"}, {es9p_ssl_disable, true}, - {eim_cert, "config/sample_eim_cert_nist.crt"}, - {eim_key, "config/sample_eim_cert_nist.key"}, + {eim_cert, "sample_eim_cert_nist.crt"}, + {eim_key, "sample_eim_cert_nist.key"}, {counter_value, 1}, {consumer_euicc, true}, {rest_timeout_stuck, 300}, {rest_timeout_noshow, 1800}, {rest_timeout_expired, 86400}, {root_ci_certs, [ - "config/sgp26_gsma_root_ci_cert_nist_symantec.crt", - "config/sgp26_gsma_root_ci_cert_nist_oiste.crt", - "config/sgp26_test_root_ci_cert_nist.crt", - "config/sgp26_test_root_ci_cert_brainpool.crt" + "sgp26_gsma_root_ci_cert_nist_symantec.crt", + "sgp26_gsma_root_ci_cert_nist_oiste.crt", + "sgp26_test_root_ci_cert_nist.crt", + "sgp26_test_root_ci_cert_brainpool.crt" ]} ]} ]. -- To view, visit https://gerrit.osmocom.org/c/onomondo-eim/+/43209?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: onomondo-eim Gerrit-Branch: master Gerrit-Change-Id: I4d8c91d787e6932fbcab7f0dcbdea620894a61c2 Gerrit-Change-Number: 43209 Gerrit-PatchSet: 1 Gerrit-Owner: dexter <pmaier(a)sysmocom.de>

1 0

[M] Change in onomondo-eim[master]: rest_api_ressource/response_schema: fix regex for hexstring fields
by dexter 12 Aug '26

12 Aug '26

dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43208?usp=email ) Change subject: rest_api_ressource/response_schema: fix regex for hexstring fields ...................................................................... rest_api_ressource/response_schema: fix regex for hexstring fields Fields which expect a hexstring use a regex to check if the string is hexadecimal. Some fields also require a hexstring of a certain length. Unfortunately some of those fields still have wrong regex. - Remove the superflous ',' in [0-9,A-F] - Correct the length requirements Related: SYS#8100 Change-Id: I00e1870bca6ca661897f55ecab6771e0c72935ea --- M priv/rest_api_resource_schema.json M priv/rest_api_response_schema.json 2 files changed, 25 insertions(+), 25 deletions(-) git pull ssh://gerrit.osmocom.org:29418/onomondo-eim refs/changes/08/43208/1 diff --git a/priv/rest_api_resource_schema.json b/priv/rest_api_resource_schema.json index c66bbaa..4ddbb8e 100644 --- a/priv/rest_api_resource_schema.json +++ b/priv/rest_api_resource_schema.json @@ -7,7 +7,7 @@ "eidValue": { "description": "EID value of the eUICC to be addressed", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{32}$" }, "order": { "description": "Order to be executed", @@ -45,7 +45,7 @@ "iccid": { "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{18,20}$" }, "rollback": { "description": "see also GSMA SGP.32, section 3.4.1, subsection 'Profile Rollback Procedure'", @@ -66,7 +66,7 @@ "iccid": { "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{18,20}$" } }, "required": [ @@ -83,7 +83,7 @@ "iccid": { "description": "ICCID of the profile. (ICCID in nibble-swapped raw format)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{18,20}$" } }, "required": [ @@ -103,14 +103,14 @@ "isdpAid": { "description": "AID of the ISDP (identifies a profile)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{2,32}$" } }, { "iccid": { "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{18,20}$" } }, { @@ -124,7 +124,7 @@ "taglist": { "description": "concatonation of the BER-TLV tags that shall be included in the response", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" } }, "required": [ @@ -227,7 +227,7 @@ "eimConfigurationData": { "description": "ASN.1 encoded EimConfigurationData", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" } }, "required": [ @@ -260,7 +260,7 @@ "eimConfigurationData": { "description": "ASN.1 encoded EimConfigurationData", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" } }, "required": [ @@ -290,7 +290,7 @@ "tagList": { "description": "see GSMA SGP.32, section 2.11.1.2", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" } }, "required": [ diff --git a/priv/rest_api_response_schema.json b/priv/rest_api_response_schema.json index 0f532d3..04ae8ce 100644 --- a/priv/rest_api_response_schema.json +++ b/priv/rest_api_response_schema.json @@ -95,12 +95,12 @@ "iccid": { "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{18,20}$" }, "isdpAid": { "description": "AID of the ISDP (identifies a profile)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{2,32}$" }, "profileState": { "description": "usage state of the prifle", @@ -129,7 +129,7 @@ "icon": { "description": "icon graphic", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "profileClass": { "description": "0=test, 1=provisioning, 2=operational", @@ -171,17 +171,17 @@ "mccMnc": { "description": "MCC and MNC coded as defined in 3GPP TS 24.008", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{3}$" }, "gid1": { "description": "referring to content of EF GID1 (file identifier '6F3E') as defined in 3GPP TS 31.102", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "gid2": { "description": "referring to content of EF GID2 (file identifier '6F3F') as defined in 3GPP TS 31.102", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" } }, "required": [ @@ -409,7 +409,7 @@ "iccid": { "description": "ICCID of the profile. (ICCID in nibble-swapped raw format, see also ETSI TS 102 221, section 13.2)", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F]{18,20}$" } }, "required": [ @@ -477,12 +477,12 @@ "euiccInfo1": { "description": "ASN.1 encoded, see GSMA SGP.22", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "euiccInfo2": { "description": "ASN.1 encoded, see GSMA SGP.22 and GSMA SGP.32", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "rootSmdsAddress": { "description": "see GSMA SGP.32", @@ -495,27 +495,27 @@ "eumCertificate": { "description": "ASN.1 encoded, see GSMA SGP.22", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "euiccCertificate": { "description": "ASN.1 encoded, see GSMA SGP.22", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "ipaCapabilities": { "description": "ASN.1 encoded, see GSMA SGP.32", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "deviceInfo": { "description": "ASN.1 encoded, see GSMA SGP.32", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" }, "notificationsList": { "description": "ASN.1 encoded, see GSMA SGP.32", "type": "string", - "pattern": "^[0-9,A-F]{2,32}$" + "pattern": "^[0-9A-F].*$" } }, "additionalProperties": false @@ -559,7 +559,7 @@ "debuginfo": { "description": "Erlang ETS encoded debug information string, for debugging/diagnosis only", "type": "string", - "pattern": "^[0-9,A-F].*$" + "pattern": "^[0-9A-F].*$" } }, "required": [ -- To view, visit https://gerrit.osmocom.org/c/onomondo-eim/+/43208?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: onomondo-eim Gerrit-Branch: master Gerrit-Change-Id: I00e1870bca6ca661897f55ecab6771e0c72935ea Gerrit-Change-Number: 43208 Gerrit-PatchSet: 1 Gerrit-Owner: dexter <pmaier(a)sysmocom.de>

1 0

[XS] Change in onomondo-eim[master]: contrib: remove onomondo-eim.service systemd example
by dexter 12 Aug '26

12 Aug '26

dexter has uploaded this change for review. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43210?usp=email ) Change subject: contrib: remove onomondo-eim.service systemd example ...................................................................... contrib: remove onomondo-eim.service systemd example The file onomondo-eim.service is is an example to illustrate how onomondo-eim could be started using systemd. However, this file is outdated and we do not use it anywhere. So let's remove it. If required, we can always add a new, working example at some later point. Related: SYS#8100 Change-Id: I78edeeb88fc1003483db996dce8e42f149ed5aff --- D contrib/onomondo-eim.service 1 file changed, 0 insertions(+), 9 deletions(-) git pull ssh://gerrit.osmocom.org:29418/onomondo-eim refs/changes/10/43210/1 diff --git a/contrib/onomondo-eim.service b/contrib/onomondo-eim.service deleted file mode 100644 index 35d8335..0000000 --- a/contrib/onomondo-eim.service +++ /dev/null @@ -1,9 +0,0 @@ -[Unit] -Description=onomondo-eim - -[Service] -Type=simple -ExecStart=/path/to/my/onomondo_eim/_rel/onomondo_eim_release/bin/onomondo_eim_release foreground - -[Install] -WantedBy=multi-user.target \ No newline at end of file -- To view, visit https://gerrit.osmocom.org/c/onomondo-eim/+/43210?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: onomondo-eim Gerrit-Branch: master Gerrit-Change-Id: I78edeeb88fc1003483db996dce8e42f149ed5aff Gerrit-Change-Number: 43210 Gerrit-PatchSet: 1 Gerrit-Owner: dexter <pmaier(a)sysmocom.de>

1 0

2026

2025

2024

2023

2022

gerrit-log August 2026