catarrh/simple
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

docs: qualify the RFM SELECT note (UICC shared FS vs ADF RFM)

Browse Source 
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.
This commit is contained in:
Антон Трошин
2026-10-05 22:37:32 +03:00
parent bf6730f028
commit c1cd86e0c2
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/test-scripts.md
+4 -2
View File
@@ -93,8 +93,10 @@ actions table).
A **scripted SELECT inside the secured packet** should ask for no response 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'` 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, 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 and the script has no use for an FCI anyway. The selects walk from the
in MF (TS 102 226 §7.2), so the selects walk from there. 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 ### Worksheet 2 - incoming data → particular PoR, no other actions