FreeCalypso > hg > fc-pcsc-tools
comparison doc/Low-level-commands @ 128:01aed8d0685a
doc/Low-level-commands: raw apdu command documented
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sat, 20 Feb 2021 20:10:18 +0000 |
| parents | 08ba6a5d8a3f |
| children | cc6a4b48dc2a |
comparison
equal
deleted
inserted
replaced
| 127:08ba6a5d8a3f | 128:01aed8d0685a |
|---|---|
| 160 match what you expect them to be. To perform this test, issue an a38 command | 160 match what you expect them to be. To perform this test, issue an a38 command |
| 161 to the SIM with some made-up RAND and note the SRES and Kc response. Then use | 161 to the SIM with some made-up RAND and note the SRES and Kc response. Then use |
| 162 the osmo-auc-gen utility from Osmocom to run the expected algorithm with the | 162 the osmo-auc-gen utility from Osmocom to run the expected algorithm with the |
| 163 expected Ki (and the expected OPc if MILENAGE is used) and the same RAND, and | 163 expected Ki (and the expected OPc if MILENAGE is used) and the same RAND, and |
| 164 see if SRES and Kc match. | 164 see if SRES and Kc match. |
| 165 | |
| 166 Exploring proprietary APDUs | |
| 167 =========================== | |
| 168 | |
| 169 If the SIM you are working with is known or suspected to implement some | |
| 170 non-standard or proprietary APDUs for which there is no explicit support in | |
| 171 fc-simtool, you can use this low-level debug command to send arbitrary APDUs: | |
| 172 | |
| 173 apdu "xx xx xx xx xx ..." | |
| 174 | |
| 175 The sole argument is a raw string of bytes (quotes are needed if there are | |
| 176 spaces between bytes), and the APDU needs to be given exactly as it is sent in | |
| 177 the T=0 protocol: 5 bytes of header (including the length byte) followed by | |
| 178 data bytes, if any. After executing the APDU exchange, the apdu command simply | |
| 179 prints the SW response code from the SIM. |