Attention is currently required from: fixeria.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37943?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified-1 by Jenkins Builder
Change subject: PFCP: fix SEID value in {ts,tr}_PFCP_Session_Est_Req
......................................................................
PFCP: fix SEID value in {ts,tr}_PFCP_Session_Est_Req
According to 3GPP TS 29.244, section 7.2.2.4.2 "Conditions for Sending
SEID=0 in PFCP Header": if a peer's SEID is not available, the SEID
field shall still be present in the header and its value shall be set
to "0" in the following messages:
* PFCP Session Establishment Request message on Sxa/Sxb/Sxc/N4;
...
Change-Id: Iacfbd68336b6fc4481c15ca5b304636df4491da4
Related: SYS#6772
---
M library/PFCP_Templates.ttcn
1 file changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/43/37943/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37943?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Iacfbd68336b6fc4481c15ca5b304636df4491da4
Gerrit-Change-Number: 37943
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: laforge, osmith.
daniel has posted comments on this change by osmith. ( https://gerrit.osmocom.org/c/docker-playground/+/37714?usp=email )
Change subject: Remove ttcn3 testsuites ported to testenv, part 1
......................................................................
Patch Set 2: Code-Review+1
(1 comment)
Patchset:
PS2:
> I thin kit makes sense to add some kind of README or other document that describes where those test […]
ACK. The README mentions testenv, but (a link to) some more documentation would be nice.
--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/37714?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: I7182c7e8eb00a9323fe1b6d27f630d253b4d34f6
Gerrit-Change-Number: 37714
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Wed, 28 Aug 2024 13:21:07 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37943?usp=email )
Change subject: PFCP: fix SEID value in {ts,tr}_PFCP_Session_Est_Req
......................................................................
PFCP: fix SEID value in {ts,tr}_PFCP_Session_Est_Req
According to 3GPP TS 29.244, section 7.2.2.4.2 "Conditions for Sending
SEID=0 in PFCP Header": if a peer's SEID is not available, the SEID
field shall still be present in the header and its value shall be set
to "0" in the following messages:
* PFCP Session Establishment Request message on Sxa/Sxb/Sxc/N4;
...
Change-Id: Iacfbd68336b6fc4481c15ca5b304636df4491da4
Related: SYS#6772
---
M library/PFCP_Templates.ttcn
1 file changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/43/37943/1
diff --git a/library/PFCP_Templates.ttcn b/library/PFCP_Templates.ttcn
index 329ea88..f4a946a 100644
--- a/library/PFCP_Templates.ttcn
+++ b/library/PFCP_Templates.ttcn
@@ -499,7 +499,7 @@
Create_PDR_list create_pdr,
Create_FAR_list create_far)
modifies ts_PDU_PFCP_ := {
- seid := omit, /* FIXME: shall be set to 0 as per 7.2.2.4.2 */
+ seid := 0, /* shall be set to 0 as per 7.2.2.4.2 */
message_body := {
pfcp_session_establishment_request := {
node_id := node_id,
@@ -519,7 +519,7 @@
template (present) PDU_PFCP
tr_PFCP_Session_Est_Req(template (present) Node_ID node_id := ?)
modifies tr_PDU_PFCP_ := {
- seid := ?,
+ seid := 0, /* shall be set to 0 as per 7.2.2.4.2 */
message_body := {
pfcp_session_establishment_request := {
node_id := node_id,
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37943?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Iacfbd68336b6fc4481c15ca5b304636df4491da4
Gerrit-Change-Number: 37943
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: laforge.
dexter has posted comments on this change by dexter. ( https://gerrit.osmocom.org/c/pysim/+/37931?usp=email )
Change subject: scp: fix key length in dek_encrypt and dek_decrypt
......................................................................
Patch Set 2:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/pysim/+/37931/comment/74c33d5e_037b1da9?usp=em… :
PS1, Line 9: When creating the DES cipher object with DES.new, we use the property
: card_keys.dek. This property may hold a 16 byte key, but DES uses
: an 8 byte key. Pycryptodome does not automatically ignore excess key
: bytes. Instead it throws an exception. This means we need to make sure
: to supply only the first 8 bytes of card_keys.dek
> did you check the spec and determie that this truncation is required/intended? IF yes, it would be […]
Yes, I have checked it. It seems to be an implementation detail of pyCryptoDome. They say: "key (bytes/bytearray/memoryview) – The secret key to use in the symmetric cipher. It must be 8 byte long. The parity bits will be ignored."
In other code locations one can find the truncation as well. I have now put a reference to the pyCryptoDome manual into the commit message. I don't think that we need an extra comment in the code, since it is only a pyCryptoDome related.
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/37931?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I92e0dc6a6196b532bd8b53fca7b9e78070d6903f
Gerrit-Change-Number: 37931
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Wed, 28 Aug 2024 12:48:55 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Attention is currently required from: laforge.
Hello Jenkins Builder, laforge,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/pysim/+/37932?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Code-Review+1 by laforge, Verified+1 by Jenkins Builder
Change subject: pySim-shell: rework startup procedure and introduce non interactive mode
......................................................................
pySim-shell: rework startup procedure and introduce non interactive mode
When pySim-shell is used in a scripted environment, we may easily get trapped in
the pySim-shell prompt. This may happen in particular in case the script file
is not executed due to problem with the reader initialization. In such a case
pySim-shell will not exit automatically and the shellscript that was calling
pySim-shell will stall indefinetly.
To make the use of pySim-shell more reliable in scripted environments, let's
add a --noprompt option that ensures the interactive mode is never entered.
Let's also exit with an appropriate return code in case of initialization
errors, so that the calling script can know that something went wrong.
Related: OS#6531
Change-Id: I07ecb27b37e2573629981a0d032cc95cd156be7e
---
M pySim-shell.py
1 file changed, 36 insertions(+), 19 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/pysim refs/changes/32/37932/2
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/37932?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I07ecb27b37e2573629981a0d032cc95cd156be7e
Gerrit-Change-Number: 37932
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>