You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Secure Channel Protocol '03'
Card Specification v2.3 - Amendment D
Version 1.2
specifies a new protocol option (i.b1) named S16 mode which, when enabled causes cards to expect 16 byte challenges, MAC values, etc., instead of the regular 8 bytes.
Information about your card and used reader
N/A
Expected behavior
S16 mode is currently not supported, resulting in cards with SCP03, i=x1 policy configuration refusing to open a secure channel. This is not a pressing issue due to card availability, but is expected to be troublesome with future card generations due to the S8 mode being referred to as legacy.
Full log
N/A
Additional context
I have quickly implemented a corresponding fix, in conjunction with more robust length checking of the INITIALIZE UPDATE response and will create a pull request in due time.
The text was updated successfully, but these errors were encountered:
Will add to the upcoming 24.10.XX release. At this point it seems a command line option -s16 is necessary (unless profiles get a bump, which does not seem to be the case now).
Describe the bug
specifies a new protocol option (i.b1) named S16 mode which, when enabled causes cards to expect 16 byte challenges, MAC values, etc., instead of the regular 8 bytes.
Information about your card and used reader
N/A
Expected behavior
S16 mode is currently not supported, resulting in cards with SCP03, i=x1 policy configuration refusing to open a secure channel. This is not a pressing issue due to card availability, but is expected to be troublesome with future card generations due to the S8 mode being referred to as legacy.
Full log
N/A
Additional context
I have quickly implemented a corresponding fix, in conjunction with more robust length checking of the INITIALIZE UPDATE response and will create a pull request in due time.
The text was updated successfully, but these errors were encountered: