Started by timerBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org00224760764760761.00005458c81e2cdf9bb1f8d831e817379cb0d03347df46b8c81e2cdf9bb1f8d831e817379cb0d03347df46borigin/master8c81e2cdf9bb1f8d831e817379cb0d03347df46b8c81e2cdf9bb1f8d831e817379cb0d03347df46borigin/master5b52b9704ed57386959a73c98e946c756e0188e6cb52b9704ed57386959a73c98e946c756e0188e6crefs/remotes/origin/osmith/wipb52b9704ed57386959a73c98e946c756e0188e6cb52b9704ed57386959a73c98e946c756e0188e6crefs/remotes/origin/osmith/wip253c7c48718ba3637e29fc6a7af4e2e39ba0679bb8dc7c48718ba3637e29fc6a7af4e2e39ba0679bb8drefs/remotes/origin/masterc7c48718ba3637e29fc6a7af4e2e39ba0679bb8dc7c48718ba3637e29fc6a7af4e2e39ba0679bb8drefs/remotes/origin/master8c81e2cdf9bb1f8d831e817379cb0d03347df46b8c81e2cdf9bb1f8d831e817379cb0d03347df46borigin/masterhttps://gerrit.osmocom.org/pysimfalse#545476076473668simtester-sanitize #545545falsefalse54571269SUCCESS1774485780440https://jenkins.osmocom.org/jenkins/job/simtester-sanitize/545/simtester- pySim/ts_51_011.py969f9c0e4bcb3cbf46be3a592315aa8a9a39e8071774449296000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.depySim/EF.SMSP: fix encoding of TP-Destination Address
The TP-Destination Address in EF.SMSP uses the same encoding as the
TS-Service Centre Address field. However, even though the encoding
of both fields looks almost identical, it actually isn't.
The TS-Service Centre Address field encodes the length field as
octets required for the call_number + one octet for ton_npi.
(see also: 3GPP TS 24.011, section 8.2.5.2)
The TP-Destination Address uses the number of digits of the
call_number directly in the length field.
(see also: 3GPP TS 23.040, section 9.1.2.5)
Related: SYS#7765
Change-Id: I55c123c9e244e5a6e71a0348f5d476ef03e618e8
2026-03-25 15:34:56 +0100969f9c0e4bcb3cbf46be3a592315aa8a9a39e807pySim/EF.SMSP: fix encoding of TP-Destination AddresseditpySim/ts_51_011.py
- pySim/global_platform/__init__.pyc7e68e1281db0fbf0e456e7807e642cb5ee49c3a1774461930000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgglobal_platform: install_cap_parser: argument groups cannot be nested
pySim-shell currently does not work on systems with Python 3.14+:
File ".../pysim/pySim/global_platform/__init__.py", line 868, in AddlShellCommands
install_cap_parser_inst_prm_g_grp = install_cap_parser_inst_prm_g.add_argument_group()
File "/usr/lib/python3.14/argparse.py", line 1794, in add_argument_group
raise ValueError('argument groups cannot be nested')
ValueError('argument groups cannot be nested')
The problem is that install_cap_parser creates a nested group inside
of mutually exclusive group. argparse never supported group nesting
properly, so it has been deprecated since Python 3.11, and eventually
got removed in Python 3.14.
Remove group nesting, adjust the usage string, and implement the
mutual exclusiveness enforcement manually in do_install_cap().
Change-Id: Idddf72d5a745345e134b23f2f01e0257d0667579
2026-03-25 18:05:30 +0000c7e68e1281db0fbf0e456e7807e642cb5ee49c3aglobal_platform: install_cap_parser: argument groups cannot be nestededitpySim/global_platform/__init__.py
- tests/unittests/test_globalplatform.pypySim/global_platform/install_param.pyd9d62ee72929fca356fd3e751e2a3284e84475ac1774461930000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgglobal_platform: refactor gen_install_parameters()
gen_install_parameters() had contradictory logic: the outer guard
required all three arguments to be non-None/non-empty (making them
mutually inclusive), while the inner checks then treated each one
as optional.
Make each parameter independently optional (defaulting to None) and
remove the all-or-nothing check. Simplify the function body to a
straightforward single-pass construction of system_specific_params.
Change-Id: I8756fb38016cdf0527fe2e21edb44381d1dc557f
2026-03-25 18:05:30 +0000d9d62ee72929fca356fd3e751e2a3284e84475acglobal_platform: refactor gen_install_parameters()editpySim/global_platform/install_param.pyedittests/unittests/test_globalplatform.py
- docs/put_key-tutorial.rstdocs/shell.rst8c81e2cdf9bb1f8d831e817379cb0d03347df46b1774462052000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgdocs/put_key: add tutorial that explains how to manage global platform keys
With the increased interest in using GlobalPlatform features of
UICC and eUICCs (OTA-SMS, applets, etc.), also comes an increased
interest in how the related GlobalPlatform keys can be managed
(key rotation, adding/removing keysets from/to a Security Domain).
Unfortunately, many aspects of this topic are not immediately
obvious for the average user. Let's add a tutorial that contains
some practical examples to shine some light on the topic.
Related: SYS#7881
Change-Id: I163dfedca3df572cb8442e9a4a280e6c5b00327e
2026-03-25 18:07:32 +00008c81e2cdf9bb1f8d831e817379cb0d03347df46bdocs/put_key: add tutorial that explains how to manage global platformeditdocs/shell.rstadddocs/put_key-tutorial.rst
githttps://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.dehttps://jenkins.osmocom.org/jenkins/user/laforgelaforge