2 Apr
2024
2 Apr
'24
2:19 p.m.
Hi James,
On Mon, Apr 01, 2024 at 10:14:40PM +0200, Harald Welte wrote:
As a quick hack, you could try the attached patch
against libosmocore.
This is just a hack to see if we really have found the culprit. It
would only work if no other part of the communication uses the UICC F2
instruction at another time. It's far from a proper solution, but worth
a try.
I've meanwile figured out that the upper 4 bits of the P1 octet are guaranteed
to be different in the ETSI UICC vs. GlobalPlatform F2 command. So we
can use those as an indicator to distinguish the two situations. See
the [still untested] patch at https://gerrit.osmocom.org/c/libosmocore/+/36501
Feel free to give that one a try and let us know if that helps.
Thanks,
Harald
--
- Harald Welte <laforge(a)osmocom.org> https://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)