Attention is currently required from: laforge, pespin, dexter.
Christian Amsüss has posted comments on this change. ( https://gerrit.osmocom.org/c/pysim/+/29033 )
Change subject: Add new pySim.ota library, implement SIM OTA crypto
......................................................................
Patch Set 5: Code-Review+1
(5 comments)
Patchset:
PS5:
Looks good to me, with some comments.
I have yet to run the encryption and integrity protection against my current reference implementation; once that passes, I'll update to +2.
File pySim/ota.py:
https://gerrit.osmocom.org/c/pysim/+/29033/comment/ddba9d13_d60daa0d
PS4, Line 44: S 102 225 Table 5
: ota_status_codes = bidict({
: 0x00: 'PoR OK',
: 0x01: 'RC/CC/DS failed',
: 0x02: 'CNTR low',
: 0x03: 'CNTR high',
: 0x04: 'CNTR blocked',
: 0x05: 'Ciphering error',
: 0x06: 'Unidentified security error',
: 0x07: 'Insufficient memory',
: 0x08: 'more time',
: 0x09: 'TAR unknown',
: 0x0a: 'Insufficient security level',
: 0x0b: 'Actual Response in SMS-SUBMIT', # 31.115
: 0x0c: 'Actual Response in USSD', # 31.115
: })
This bidict is redundant with ResponseStatus, and not used anywhere. Maybe left over from earlier revisions?
https://gerrit.osmocom.org/c/pysim/+/29033/comment/00b05de6_921f8369
PS4, Line 120: algo_auth: str, kid_idx: int, kid: bytes, cntr: int = 0):
I'm very suspicious of the counter having zero as a default; the symmetric algorithm is already initialized with a zero IV, the CNTR and some of the other early bytes kind of take its place after the first round of encryption. I'm not an expert there, but unless someone who knows all the involved algorithms well tells me that this kind of nonce reuse is OK, I'd prefer APIs that guide users towards explicit monotonous CNTR values.
File pySim/sms.py:
https://gerrit.osmocom.org/c/pysim/+/29033/comment/c397e2d1_9844a98e
PS5, Line 30: ie_c = Struct('offset'/Tell, 'iei'/Int8ub, 'length'/Int8ub, 'data'/Bytes(this.length))
There is an updated version of this in your patch series, which is easier to understand and removes the FIXME.
https://gerrit.osmocom.org/c/pysim/+/29033/comment/b33ba117_4cde9e79
PS5, Line 39: def __str__(self) -> str:
I think this would be more useful as `__repr__`, especially as it does produce an expression that'd recreate the object (ref: <https://docs.python.org/3/reference/datamodel.html#object.__repr__>). The %s could become %r but likely makes no difference for the typical list of ies.
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/29033
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I193ff4712c8503279c017b4b1324f0c3d38b9f84
Gerrit-Change-Number: 29033
Gerrit-PatchSet: 5
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Christian Amsüss <chrysn(a)fsfe.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 19 Aug 2022 15:41:19 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
fixeria has abandoned this change. ( https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/29160 )
Change subject: Fix handling of Re-Synchronization-Info AVP in AIR
......................................................................
Abandoned
You're welcome!
--
To view, visit https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/29160
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: erlang/osmo_dia2gsup
Gerrit-Branch: master
Gerrit-Change-Id: Ie5eded2f5fb2de01f69d2a9c0e5d70283bf5cbf5
Gerrit-Change-Number: 29160
Gerrit-PatchSet: 3
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: abandon
Attention is currently required from: laforge, fixeria.
daniel has posted comments on this change. ( https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/29160 )
Change subject: Fix handling of Re-Synchronization-Info AVP in AIR
......................................................................
Patch Set 3: Code-Review-1
(1 comment)
Patchset:
PS3:
I tried, but something was still off. https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/20021 did work though, so I merged that instead. In any case thanks for the help!
--
To view, visit https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/29160
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: erlang/osmo_dia2gsup
Gerrit-Branch: master
Gerrit-Change-Id: Ie5eded2f5fb2de01f69d2a9c0e5d70283bf5cbf5
Gerrit-Change-Number: 29160
Gerrit-PatchSet: 3
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 19 Aug 2022 15:35:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: msuraev.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-sccp/+/29159 )
Change subject: cosmetic: constify function parameters, return proper error
......................................................................
Patch Set 1: Code-Review-1
(3 comments)
Commit Message:
https://gerrit.osmocom.org/c/libosmo-sccp/+/29159/comment/8dc9229f_2543b9c4
PS1, Line 7: cosmetic: constify function parameters, return proper error
the summary should indicate the scope ("sccp_scoc.c:...")
Patchset:
PS1:
please separate "constify" and "change rc" in distinct commits
File src/sccp_scoc.c:
https://gerrit.osmocom.org/c/libosmo-sccp/+/29159/comment/a872b49f_f0fa1b93
PS1, Line 704: return -ENOMSG;
-ENOMEM would be the proper code here.
but actually, none of the callers even look at the return code. what is this change about?
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sccp/+/29159
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-sccp
Gerrit-Branch: master
Gerrit-Change-Id: I398e3efa3e097de8907617cfdf363e1d3b96f666
Gerrit-Change-Number: 29159
Gerrit-PatchSet: 1
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 19 Aug 2022 14:49:58 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: msuraev.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-netif/+/29082 )
Change subject: Log more details in osmo_stream_srv_write()
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/libosmo-netif/+/29082/comment/80d6a6e6_eb3b114b
PS1, Line 9: Log error code and amount of data - both are handy for debugging apps using the library.
commit log line width is typically 72
this summarizes well:
https://stackoverflow.com/questions/2290016/git-commit-messages-50-72-forma…
--
To view, visit https://gerrit.osmocom.org/c/libosmo-netif/+/29082
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-netif
Gerrit-Branch: master
Gerrit-Change-Id: I580c00f3b5ade05ecb20a92ce4ece2854334a41f
Gerrit-Change-Number: 29082
Gerrit-PatchSet: 1
Gerrit-Owner: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: msuraev <msuraev(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 19 Aug 2022 14:44:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment