release: v3.9.1 - the counter probe sends a fixed read-only APDU
- The probe no longer takes a caller-supplied `apdu`: it always sends the read-only SELECT MF (the counter advances on the packet's security acceptance whatever the applet answers - 6A86/6D00 are normal there), so no caller can turn the sync probe into a write. - Version 3.9.1: server VERSION, pyproject.toml and the PWA header; sw cache simple-v357; docs/api.md and the repo AGENTS.md updated, and the workspace AGENTS.md gains the v3.9.1 history entry (its "Currently" line was stale at v3.7.1).
This commit is contained in:
@@ -32,7 +32,7 @@ from osmocom.tlv import BER_TLV_IE
|
||||
from osmocom.utils import rpad
|
||||
|
||||
|
||||
VERSION = '3.9.0'
|
||||
VERSION = '3.9.1'
|
||||
|
||||
MAX_ENVELOPE_SEGMENTS = 5 # max SMS segments for outgoing C-APDU in ENVELOPE
|
||||
|
||||
@@ -1668,7 +1668,10 @@ def _counter_probe_params(preset, body):
|
||||
'spi1': spi1,
|
||||
'spi2': str(body.get('spi2') or preset.get('spi2') or '21').strip().upper(),
|
||||
'tar': str(body.get('tar') or preset.get('tar') or '000000').strip().upper(),
|
||||
'apdu': str(body.get('apdu') or COUNTER_PROBE_DEFAULT_APDU).replace(' ', '').upper(),
|
||||
# the probe command is fixed: read-only SELECT MF, which every applet
|
||||
# answers (an error SW is fine - the counter advances on the packet's
|
||||
# security acceptance, not on the command's own result)
|
||||
'apdu': COUNTER_PROBE_DEFAULT_APDU,
|
||||
}
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user