Attention is currently required from: laforge.
Jenkins Builder has posted comments on this change. ( https://gerrit.osmocom.org/c/pysim/+/35461?usp=email )
Change subject: Initial work on a SM-DP+ for GSMA consumer eSIM RSP
......................................................................
Patch Set 3:
(1 comment)
File tests/test_esim_bsp.py:
Robot Comment from checkpatch (run ID jenkins-gerrit-lint-13460):
https://gerrit.osmocom.org/c/pysim/+/35461/comment/8faf1298_248eb5f2
PS3, Line 73: """This test verifies whether some fully encoded/encrypted/MACed bound profile pacakge can be properly
'pacakge' may be misspelled - perhaps 'package'?
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/35461?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I6232847432dc6920cd2bd08c84d7099c29ca1c11
Gerrit-Change-Number: 35461
Gerrit-PatchSet: 3
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Fri, 05 Jan 2024 22:57:51 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: laforge.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/pysim/+/35461?usp=email
to look at the new patch set (#3).
The following approvals got outdated and were removed:
Verified-1 by Jenkins Builder
Change subject: Initial work on a SM-DP+ for GSMA consumer eSIM RSP
......................................................................
Initial work on a SM-DP+ for GSMA consumer eSIM RSP
This commit introduces
* the osmo-smdpp.py program implementing the main procedures and the
HTTP/REST based ES9+
* python modules for ES8+ and non-volatile RSP Session State storage
* the ASN.1 source files required to parse/encode RSP
* 3GPP test certificates from SGP.26
* an unsigned profile package (UPP) of a SAIP v2.3 TS48 test profile
As I couldn't get the 'Klein' tls support to work, the SM-DP+ code
currently does not support HTTPS/TLS but plan HTTP, so you either have
to modify your LPA to use HTTP instead of HTTPS, or put a TLS proxy in
front.
The SM-DP+ is currently failing (at least with my test-eUICC) during
configureIsdp with scp03tSecurityError - despite all parts (BSP, KDF,
ECKA, ...) having been verified agains hexdumps from a third party
implementation.
Change-Id: I6232847432dc6920cd2bd08c84d7099c29ca1c11
---
A .checkpatch.conf
A osmo-smdpp.py
M pySim/esim/__init__.py
A pySim/esim/asn1/rsp/PKIX1Explicit88.asn
A pySim/esim/asn1/rsp/PKIX1Implicit88.asn
A pySim/esim/asn1/rsp/rsp.asn
A pySim/esim/es8p.py
A pySim/esim/rsp.py
A smdpp-data/certs/CertificateIssuer/CERT_CI_ECDSA_BRP.der
A smdpp-data/certs/CertificateIssuer/CERT_CI_ECDSA_BRP.pem
A smdpp-data/certs/CertificateIssuer/CERT_CI_ECDSA_NIST.der
A smdpp-data/certs/CertificateIssuer/CERT_CI_ECDSA_NIST.pem
A smdpp-data/certs/CertificateIssuer/CI-csr.cnf
A smdpp-data/certs/DPauth/CERT_S_SM_DP2auth_ECDSA_BRP.der
A smdpp-data/certs/DPauth/CERT_S_SM_DP2auth_ECDSA_NIST.der
A smdpp-data/certs/DPauth/CERT_S_SM_DPauth_ECDSA_BRP.der
A smdpp-data/certs/DPauth/CERT_S_SM_DPauth_ECDSA_NIST.der
A smdpp-data/certs/DPauth/PK_S_SM_DP2auth_ECDSA_BRP.pem
A smdpp-data/certs/DPauth/PK_S_SM_DP2auth_ECDSA_NIST.pem
A smdpp-data/certs/DPauth/PK_S_SM_DPauth_ECDSA_BRP.pem
A smdpp-data/certs/DPauth/PK_S_SM_DPauth_ECDSA_NIST.pem
A smdpp-data/certs/DPauth/SK_S_SM_DP2auth_ECDSA_BRP.pem
A smdpp-data/certs/DPauth/SK_S_SM_DP2auth_ECDSA_NIST.pem
A smdpp-data/certs/DPauth/SK_S_SM_DPauth_ECDSA_BRP.pem
A smdpp-data/certs/DPauth/SK_S_SM_DPauth_ECDSA_NIST.pem
A smdpp-data/certs/DPauth/data_sig.der
A smdpp-data/certs/DPpb/CERT_S_SM_DP2pb_ECDSA_BRP.der
A smdpp-data/certs/DPpb/CERT_S_SM_DP2pb_ECDSA_NIST.der
A smdpp-data/certs/DPpb/CERT_S_SM_DPpb_ECDSA_BRP.der
A smdpp-data/certs/DPpb/CERT_S_SM_DPpb_ECDSA_NIST.der
A smdpp-data/certs/DPpb/PK_S_SM_DP2pb_ECDSA_BRP.pem
A smdpp-data/certs/DPpb/PK_S_SM_DP2pb_ECDSA_NIST.pem
A smdpp-data/certs/DPpb/PK_S_SM_DPpb_ECDSA_BRP.pem
A smdpp-data/certs/DPpb/PK_S_SM_DPpb_ECDSA_NIST.pem
A smdpp-data/certs/DPpb/SK_S_SM_DP2pb_ECDSA_BRP.pem
A smdpp-data/certs/DPpb/SK_S_SM_DP2pb_ECDSA_NIST.pem
A smdpp-data/certs/DPpb/SK_S_SM_DPpb_ECDSA_BRP.pem
A smdpp-data/certs/DPpb/SK_S_SM_DPpb_ECDSA_NIST.pem
A smdpp-data/certs/DPtls/CERT_S_SM_DP2_TLS.csr.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP2_TLS.der
A smdpp-data/certs/DPtls/CERT_S_SM_DP2_TLS.ext.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP4_TLS.csr.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP4_TLS.der
A smdpp-data/certs/DPtls/CERT_S_SM_DP4_TLS.ext.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP8_TLS.csr.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP8_TLS.der
A smdpp-data/certs/DPtls/CERT_S_SM_DP8_TLS.ext.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP_TLS.csr.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP_TLS.ext.cnf
A smdpp-data/certs/DPtls/CERT_S_SM_DP_TLS_BRP.der
A smdpp-data/certs/DPtls/CERT_S_SM_DP_TLS_NIST.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2021/CERT_S_SM_DP2_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2021/CERT_S_SM_DP4_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2021/CERT_S_SM_DP8_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2021/CERT_S_SM_DP_TLS_BRP.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2021/CERT_S_SM_DP_TLS_NIST.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2022/CERT_S_SM_DP2_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2022/CERT_S_SM_DP4_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2022/CERT_S_SM_DP8_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2022/CERT_S_SM_DP_TLS_BRP.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2022/CERT_S_SM_DP_TLS_NIST.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2023/CERT_S_SM_DP2_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2023/CERT_S_SM_DP4_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2023/CERT_S_SM_DP8_TLS.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2023/CERT_S_SM_DP_TLS_BRP.der
A smdpp-data/certs/DPtls/Old_TLS_Validity/Expired 2023/CERT_S_SM_DP_TLS_NIST.der
A smdpp-data/certs/DPtls/PK_S_SM_DP2_TLS_NIST.pem
A smdpp-data/certs/DPtls/PK_S_SM_DP4_TLS.pem
A smdpp-data/certs/DPtls/PK_S_SM_DP8_TLS.pem
A smdpp-data/certs/DPtls/PK_S_SM_DP_TLS_BRP.pem
A smdpp-data/certs/DPtls/PK_S_SM_DP_TLS_NIST.pem
A smdpp-data/certs/DPtls/SK_S_SM_DP2_TLS_NIST.pem
A smdpp-data/certs/DPtls/SK_S_SM_DP4_TLS.pem
A smdpp-data/certs/DPtls/SK_S_SM_DP8_TLS.pem
A smdpp-data/certs/DPtls/SK_S_SM_DP_TLS_BRP.pem
A smdpp-data/certs/DPtls/SK_S_SM_DP_TLS_NIST.pem
A smdpp-data/certs/README
A smdpp-data/upp/TS48 V2 eSIM_GTP_SAIP2.3_NoBERTLV.rename2der
A tests/test_esim.py
M tests/test_esim_bsp.py
80 files changed, 3,083 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/pysim refs/changes/61/35461/3
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/35461?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I6232847432dc6920cd2bd08c84d7099c29ca1c11
Gerrit-Change-Number: 35461
Gerrit-PatchSet: 3
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newpatchset
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/pysim/+/35461?usp=email )
Change subject: Initial work on a SM-DP+ for GSMA consumer eSIM RSP
......................................................................
Patch Set 2:
This change is ready for review.
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/35461?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I6232847432dc6920cd2bd08c84d7099c29ca1c11
Gerrit-Change-Number: 35461
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Comment-Date: Fri, 05 Jan 2024 22:53:11 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: laforge.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/pysim/+/35488?usp=email
to look at the new patch set (#3).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
Change subject: Add pySim.esim.bsp module implementing BSP (BPP Protection Protocol)
......................................................................
Add pySim.esim.bsp module implementing BSP (BPP Protection Protocol)
This is the protocol used for the ES8+ interface between SM-DP+ and the
eUICC in the GSMA eSIM system.
Change-Id: Ic461936f2e68e1e6f7faab33d06acf3063e261e7
---
A pySim/esim/__init__.py
A pySim/esim/bsp.py
M requirements.txt
A tests/test_esim_bsp.py
4 files changed, 395 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/pysim refs/changes/88/35488/3
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/35488?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: Ic461936f2e68e1e6f7faab33d06acf3063e261e7
Gerrit-Change-Number: 35488
Gerrit-PatchSet: 3
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newpatchset
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/35490?usp=email )
Change subject: GTPv2_Emulation: Improve routing messages to client
......................................................................
GTPv2_Emulation: Improve routing messages to client
Before this patch, for instance, registering an IMSI would not
necessarily mean the messaged ended up in the client registering it, due
to how the code paths were being handled.
Ideally the code should create a CLIENT candidate list based on all
registered matches, and then remove duplicates and finally send message
to each CLIENT in the resulting list. That's really not needed as of now
though.
Change-Id: If253a2b8991f0caf685058238df9a7c997983e27
---
M library/GTPv2_Emulation.ttcn
1 file changed, 53 insertions(+), 21 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/90/35490/1
diff --git a/library/GTPv2_Emulation.ttcn b/library/GTPv2_Emulation.ttcn
index 0b2cb4f..eb2b977 100644
--- a/library/GTPv2_Emulation.ttcn
+++ b/library/GTPv2_Emulation.ttcn
@@ -107,6 +107,16 @@
GTP2_ConnHdlr vc_conn
};
+private function f_teid_known(OCT4 teid) runs on GTPv2_Emulation_CT return boolean {
+ var integer i;
+ for (i := 0; i < sizeof(TidTable); i := i+1) {
+ if (isbound(TidTable[i].teid) and TidTable[i].teid == teid) {
+ return true;
+ }
+ }
+ return false;
+}
+
private function f_comp_by_teid(OCT4 teid) runs on GTPv2_Emulation_CT return GTP2_ConnHdlr {
var integer i;
for (i := 0; i < sizeof(TidTable); i := i+1) {
@@ -139,6 +149,16 @@
mtc.stop;
}
+private function f_imsi_known(hexstring imsi) runs on GTPv2_Emulation_CT return boolean {
+ var integer i;
+ for (i := 0; i < sizeof(ImsiTable); i := i+1) {
+ if (isbound(ImsiTable[i].imsi) and ImsiTable[i].imsi == imsi) {
+ return true;
+ }
+ }
+ return false;
+}
+
private function f_comp_by_imsi(hexstring imsi) runs on GTPv2_Emulation_CT return GTP2_ConnHdlr {
var integer i;
for (i := 0; i < sizeof(ImsiTable); i := i+1) {
@@ -540,30 +560,24 @@
/* route inbound GTP2-C based on TEID, SEQ or IMSI */
[] GTP2C.receive(Gtp2cUnitdata:?) -> value g2c_ud {
var template hexstring imsi_t := f_gtp2c_extract_imsi(g2c_ud.gtpc);
- if (not ispresent(g2c_ud.gtpc.tEID) or g2c_ud.gtpc.tEID == int2oct(0, 4)) {
- /* if this is a response, route by SEQ */
- if (match(g2c_ud.gtpc, tr_PDU_GTP2C_msgtypes(gtp2_responses))
- and f_seq_known(g2c_ud.gtpc.sequenceNumber)) {
- vc_conn := f_comp_by_seq(g2c_ud.gtpc.sequenceNumber);
- CLIENT.send(g2c_ud.gtpc) to vc_conn;
- } else {
- SendToUdMsgTable(g2c_ud);
- TEID0.send(g2c_ud.gtpc);
- }
- } else if (ispresent(g2c_ud.gtpc.tEID) and g2c_ud.gtpc.tEID != int2oct(0, 4)) {
- vc_conn := f_comp_by_teid(g2c_ud.gtpc.tEID);
- CLIENT.send(g2c_ud.gtpc) to vc_conn;
- } else if (isvalue(imsi_t)) {
+ if (isvalue(imsi_t) and f_imsi_known(valueof(imsi_t))) {
vc_conn := f_comp_by_imsi(valueof(imsi_t));
CLIENT.send(g2c_ud.gtpc) to vc_conn;
+ } else if ((ispresent(g2c_ud.gtpc.tEID) and g2c_ud.gtpc.tEID != '00000000'O)
+ and f_teid_known(g2c_ud.gtpc.tEID)) {
+ vc_conn := f_comp_by_teid(g2c_ud.gtpc.tEID);
+ CLIENT.send(g2c_ud.gtpc) to vc_conn;
+ } else if ((not ispresent(g2c_ud.gtpc.tEID) or g2c_ud.gtpc.tEID == '00000000'O)
+ and f_teid_known('00000000'O)) {
+ vc_conn := f_comp_by_teid(g2c_ud.gtpc.tEID);
+ CLIENT.send(g2c_ud.gtpc) to vc_conn;
+ /* if this is a response, route by SEQ: */
+ } else if (match(g2c_ud.gtpc, tr_PDU_GTP2C_msgtypes(gtp2_responses))
+ and f_seq_known(g2c_ud.gtpc.sequenceNumber)) {
+ vc_conn := f_comp_by_seq(g2c_ud.gtpc.sequenceNumber);
+ CLIENT.send(g2c_ud.gtpc) to vc_conn;
} else {
- /* Send to all clients */
- var integer i;
- for (i := 0; i < sizeof(TidTable); i := i+1) {
- if (isbound(TidTable[i].teid) and TidTable[i].teid == teid) {
- CLIENT.send(g2c_ud.gtpc) to TidTable[i].vc_conn;
- }
- }
+ SendToUdMsgTable(g2c_ud);
}
/* remove sequence number if response was received */
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/35490?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: If253a2b8991f0caf685058238df9a7c997983e27
Gerrit-Change-Number: 35490
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: fixeria.
Hello Jenkins Builder, laforge, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmocore/+/35481?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
The change is no longer submittable: Verified is unsatisfied now.
Change subject: tests/tdef: improve test output (use OSMO_T_FMT[_ARGS])
......................................................................
tests/tdef: improve test output (use OSMO_T_FMT[_ARGS])
Change-Id: Ie216bcf93b96610c46c6e616835a6793772e2baa
Related: e30d22a0 "tests/tdef: also test OSMO_TDEF_US and negative T values"
---
M tests/tdef/tdef_test.c
M tests/tdef/tdef_test.ok
2 files changed, 26 insertions(+), 15 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/81/35481/2
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/35481?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Ie216bcf93b96610c46c6e616835a6793772e2baa
Gerrit-Change-Number: 35481
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: fixeria.
Hello Jenkins Builder, laforge, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmocore/+/35482?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
The change is no longer submittable: Verified is unsatisfied now.
Change subject: fsm: fix OSMO_T_FMT_ARGS: add missing braces
......................................................................
fsm: fix OSMO_T_FMT_ARGS: add missing braces
Change-Id: I3ea7cbc8a51d310d9929ca5a805eb1d3d3880793
---
M include/osmocom/core/fsm.h
1 file changed, 10 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/82/35482/2
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/35482?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I3ea7cbc8a51d310d9929ca5a805eb1d3d3880793
Gerrit-Change-Number: 35482
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: laforge, neels, pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/35466?usp=email )
Change subject: core: osmo_tdef_fsm_inst_state_chg(): allow millisecond precision
......................................................................
Patch Set 6:
(1 comment)
Patchset:
PS4:
> So if it's not a lot of work, yes, having _uS granularity would be nice.
In the case of `OSMO_TDEF_MS`, I am simply migrating this tdef API to use the **existing** `osmo_fsm_..._ms()` API. There is currently no `osmo_fsm_..._us()` API, so supporting `OSMO_TDEF_US` would mean adding the missing osmo_fsm API. This is indeed more work, and I don't think I can spend even more time on this.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/35466?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I4c4ee89e7e32e86f74cd215f5cbfa44ace5426c1
Gerrit-Change-Number: 35466
Gerrit-PatchSet: 6
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 05 Jan 2024 15:48:24 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: comment