Attention is currently required from: fixeria, laforge, pespin.
1 comment:
File pySim/esim/saip/__init__.py:
So, when SUCI-CalcInfo for USIM in DF.SAIP contains both key types,
# then no profile-A or B services need to be requested explicitly.
I'm not sure you can go about it that way. […]
I've looked it up specifically to solve the problem of requiring BOTH even though only one of them is strictly necessary like discussed in SYS#8096.
quoting SAIP spec (and SYS#8096)
SAIP 2.3.1, 8.2 Profile Header:
[...]
• get-identity: support of the GET IDENTITY as defined in ETSI [102 221] and the associated interface
for SUCI derivation defined in 3GPP [31.130]. __*At least one implementation of the ECIES profile A or
profile B*__ as described in 3GPP [33.501] shall be supported by the eUICC when this function is
supported. The Null-scheme shall be supported in addition of the ECIES scheme. This service shall
be set in the Profile if services n°124 and n°125 are "available" in EF UST
• profile-a-x25519: implementation of the ECIES Profile A as described in 3GPP [33.501]
• profile-b-p256: implementation of the ECIES Profile B as described in 3GPP [33.501]
The point here is that get-identity implies:
"one of A or B in addition to Null-key support"
Please confirm and mark resolved, thx
To view, visit change 42829. To unsubscribe, or for help writing mail filters, visit settings.