From c1cd86e0c2a496a5bd402bfb539b4df73eb87751 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, 5 Oct 2026 22:37:32 +0300 Subject: [PATCH] docs: qualify the RFM SELECT note (UICC shared FS vs ADF RFM) The scripted-SELECT note cited TS 102 226 7.2 alone although the paragraph right above lists both B00000 and B00001: 7.2 is the UICC shared FS RFM application (implicitly selected in MF), while an ADF RFM application starts in its ADF (7.3). Also says the script has no *use* for an FCI rather than nowhere to put it. --- docs/test-scripts.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/test-scripts.md b/docs/test-scripts.md index d61a7ab..8908638 100644 --- a/docs/test-scripts.md +++ b/docs/test-scripts.md @@ -93,8 +93,10 @@ actions table). A **scripted SELECT inside the secured packet** should ask for no response data (`P2='0C'`, e.g. `00A4000C02A153`): a card can refuse the `P2='00'` form (return the FCI) with `6A86` when it arrives inside a command script, -and the script has nowhere to put an FCI anyway. The RFM application starts -in MF (TS 102 226 §7.2), so the selects walk from there. +and the script has no use for an FCI anyway. The selects walk from the +current directory the RFM application starts in: MF for the UICC shared FS +RFM application (TAR `B00000`, TS 102 226 §7.2), the ADF for an ADF RFM +application (TAR `B00001`, §7.3). ### Worksheet 2 - incoming data → particular PoR, no other actions