852eff54df
ETSI TS 102 221, section 7.3 specifies that UICCs (and eUICCs) may support two different transport protocols: T=0 or T=1 or both. The spec also says that the terminal must support both protocols. This patch adds the necessary functionality to support the T=1 protocol alongside the T=0 protocol. However, this also means that we have to sharpen the lines between APDUs and TPDUs. As this patch also touches the low level interface to readers it was also manually tested with a classic serial reader. Calypso and AT command readers were not tested. Change-Id: I8b56d7804a2b4c392f43f8540e0b6e70001a8970 Related: OS#6367
21 lines
815 B
Plaintext
21 lines
815 B
Plaintext
set debug true
|
|
set echo true
|
|
set apdu_trace true
|
|
|
|
# Case #1: (open channel #1)
|
|
# No command data field, No response data field present
|
|
# (in ISO/IEC 7816-3 format, this APDU would lack the 0x00 at the end)
|
|
apdu 0070000100 --expect-sw 9000 --expect-response-regex '^$'
|
|
|
|
# Case #2: (status)
|
|
# No command data field, Response data field present
|
|
apdu 80F2000000 --expect-sw 9000 --expect-response-regex '^[a-fA-F0-9]+$'
|
|
|
|
# Case #3: (terminal capability)
|
|
# Command data field present, No response data field
|
|
apdu 80AA000005a903830180 --expect-sw 9000 --expect-response-regex '^$'
|
|
|
|
# Case #4: (select MF)
|
|
# Command data field present, Response data field present
|
|
# (in ISO/IEC 7816-3 format, this APDU would have an additional 0x00 at the end)
|
|
apdu 00a40004023f00 --expect-sw 9000 --expect-response-regex '^[a-fA-F0-9]+$' |