ui: start the SELECT picker session in MF for both RFM builders
The file picker's implicit current DF now defaults to MF for SIM RFM and USIM RFM alike (the real context follows the TAR the packet is sent to, TS 102 226 7.2/7.3, so the default is neutral and the per-row "starts in" selector covers ADF sessions - ADF.USIM files appear once it is switched). Tests set the ADF session explicitly where they exercise ADF-relative fills plus a new default assertion; help 2.1 EN/RU, READMEs and AGENTS updated. sw cache -> simple-v244; version stays 3.4.0.
This commit is contained in:
+1
-1
@@ -98,7 +98,7 @@
|
||||
<p class="text-sm mb-2">Every SELECT row has a file picker below the method fields: a filter box, an <strong>all files</strong> toggle, the session start root with the current DF, and the file list grouped by root (<code class="font-mono text-sm">MF</code>, <code class="font-mono text-sm">ADF.USIM</code>, …). Picking a file fills the fields for the current method; when the method cannot express the selection the picker switches to one that can — preferring <strong>path</strong> (one SELECT), else <strong>chain</strong> — and says so in the note line, e.g. a file under another DF becomes <code class="font-mono text-sm">7F106F40</code> (path from MF) or <code class="font-mono text-sm">7F20,6F46</code> (relative FID chain).</p>
|
||||
<ul class="list-disc list-inside text-sm space-y-1 mb-3">
|
||||
<li><strong>List source</strong>: with a card equipped the loaded file-manager tree wins (card names and probed presence; probed-absent files are hidden). Without a card, or for branches the tree has not loaded, the shipped standard list is used — <code class="font-mono text-sm">uicc_files.json</code>, generated from pySim's profiles/application classes by <code class="font-mono text-sm">pysim_simple_server/uicc_files.py</code> and kept in sync by a test. The list is specs-default until you run <strong>Probe all files</strong> in the file manager. Custom files are always merged.</li>
|
||||
<li><strong>Session start</strong>: the implicit current DF depends on the <em>TAR</em> the secured packet is sent to — the UICC Shared File System RFM application starts in MF (TS 102 226 §7.2), an ADF RFM application in its ADF (§7.3). The picker defaults to MF for this builder and ADF.USIM for USIM RFM (matching the preset TARs) and can be changed per row.</li>
|
||||
<li><strong>Session start</strong>: the implicit current DF depends on the <em>TAR</em> the secured packet is sent to — the UICC Shared File System RFM application starts in MF (TS 102 226 §7.2), an ADF RFM application in its ADF (§7.3). The picker defaults to MF for both builders and can be changed per row (select the ADF to work in an ADF session).</li>
|
||||
<li><strong>Path</strong> is the FID sequence from MF <em>without</em> the MF identifier (ISO 7816-4: “select from the MF — path without the MF identifier”); the USIM <strong>from current DF</strong> variant uses the relative tail. <strong>Chain</strong> stays relative to the current DF and follows the FID search order of TS 102 221 §11.1.1.2 (children → parent → siblings), so it never needs a hop to the common ancestor itself.</li>
|
||||
<li>ADF roots are not pickable: an application is selected by AID, which the <strong>By AID</strong> method keeps manual (TS 102 226 §7.1 forbids P1=<code class="font-mono text-sm">04</code> for RFM).</li>
|
||||
</ul>
|
||||
|
||||
Reference in New Issue
Block a user