From 6f058392f80cfc827f67c120b62a4e1933fd35d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=90=D0=BD=D1=82=D0=BE=D0=BD=20=D0=A2=D1=80=D0=BE=D1=88?= =?UTF-8?q?=D0=B8=D0=BD?= Date: Mon, 24 Aug 2026 21:23:05 +0300 Subject: [PATCH] README: document client-side secured-packet decryption --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1d8d431..045df50 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,11 @@ that both captures APDU traffic and serves that PWA. - SMS TPDU — SMS-DELIVER/SUBMIT, SCTS timestamps, UDH information elements - SCP80 OTA secured packets — SPI bits (ciphering, PoR requirement/mode, RC/CC/DS, counter), KIc/KID algorithm + key set, TAR, CNTR/PCNTR; - Response Packet (PoR) decode on GET RESPONSE + Response Packet (PoR) decode on GET RESPONSE; **optional client-side + decryption** of ciphered packets — paste the card's 3DES/AES key in the + detail view to reveal the real CNTR and secured application data (the + key stays in the browser, in-memory only; ciphered on-wire CNTR/PCNTR/RC + are ciphertext and labeled as such) - ATR parse (clock-rate conversion, Fi/Di, T-bitmask) and FCP/FCI TLV **simtrace-analyser PWA** ([`frontend/`](frontend/)):