SysmoUSIM-SJS1 » History » Version 12
dexter, 02/24/2017 09:34 AM
| 1 | 4 | {{>toc}} |
|
|---|---|---|---|
| 2 | 1 | ||
| 3 | 4 | h1. sysmoUSIM-SJS1 |
|
| 4 | |||
| 5 | 1 | The sysmoUSIM-SJS1 is programmable and Java capable USIM card. Not all commands are known yet and this page should grow over time. Each card is using a separate ADM1 key and the default configuration is hacker/developer friendly (fields being writable, reduced security for installing applets to have more quick development cycles). |
|
| 6 | 3 | ||
| 7 | Please see [[shadysim.py]] for a tutorial on installing and removing a SIM Toolkit. |
||
| 8 | 1 | ||
| 9 | |||
| 10 | 5 | laforge | h2. User Manual |
| 11 | |||
| 12 | sysmocom provides a user manual at https://www.sysmocom.de/downloads/sysmousim-manual.pdf |
||
| 13 | 1 | ||
| 14 | 9 | dexter | |
| 15 | 10 | dexter | h2. Tools |
| 16 | |||
| 17 | 12 | dexter | The sysmoUSIM-SJS1 can be parameterized using pySim and sysmo-usim-tool. PySim provides the common general bulk provisioning features, which are already known from MagicSIM and previous sysmocom simcard models. Most of the settings (like Ki, ICCIC, OPC, etc...) listed below are covered by PySim. For tweaking higly sysmoUSIM-SJS1 specific parameters (authentication algorithms, milenage parameters, enable/disable USIM application etc...), sysmo-usim-tool can be used. For more information see manual section "7.2 sysmo-usim-tool" in the provided manual. |
| 18 | |||
| 19 | See also *pySim-prog.py* program from git://git.osmocom.org/pysim (http://git.osmocom.org/pysim/) and *sysmo-usim-tool* program from git://git.sysmocom.de/sysmo-usim-tool (http://git.sysmocom.de/sysmo-usim-tool) |
||
| 20 | 10 | dexter | |
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | |||
| 25 | 6 | laforge | h2. Availability |
| 26 | |||
| 27 | sysoUSIM-SJS1 is available from http://shop.sysmocom.de/ in both 2FF+3FF (micro) and 2FF+4FF (nano) form factors. |
||
| 28 | 1 | ||
| 29 | 9 | dexter | |
| 30 | 4 | h2. Command Reference |
|
| 31 | |||
| 32 | 1 | To understand this reference, it is assumed that you are familiar with basic knowledge on smartcard |
|
| 33 | technologies, such as standard ISO 7816-3/-4 APDUs and GSM TS 11.11. |
||
| 34 | |||
| 35 | The below should be possible to set after authenticating with the ADM1 pin |
||
| 36 | |||
| 37 | |||
| 38 | 4 | h3. Setting the IMSI |
|
| 39 | |||
| 40 | 1 | Use a standard UPDATE BINARY command on EF.IMSI (7F20/6F07) |
|
| 41 | |||
| 42 | |||
| 43 | 4 | h3. Setting the ICCID |
|
| 44 | |||
| 45 | 1 | Use a standard UPDATE BINARY command on EF.ICCID (2FE2) |
|
| 46 | |||
| 47 | |||
| 48 | h3. Setting the Ki |
||
| 49 | 4 | ||
| 50 | 1 | Use a standard UPATE BINARY command on EF.KI (7F20/00FF) |
|
| 51 | |||
| 52 | |||
| 53 | 9 | dexter | h3. Setting the OP/OPC |
| 54 | 1 | ||
| 55 | 9 | dexter | Use a standard UPATE BINARY command on the EF.OPC (7F20/00F7) |
| 56 | 4 | ||
| 57 | 9 | dexter | |_. Offset |_. Size |_. Description | |
| 58 | |0|1| 0x00 for OP, 0x01 for OPc| |
||
| 59 | |1|16|OP or OPc value, depending on byte at offset 0| |
||
| 60 | 1 | ||
| 61 | 4 | ||
| 62 | h3. Setting the Algorithm(s) |
||
| 63 | 2 | ||
| 64 | Use a standard UPDATE BINARY command on EF.AUTH (7FCC/6F00) |
||
| 65 | |||
| 66 | Two bytes, first byte for 2G, second byte for 3G. |
||
| 67 | 1 | ||
| 68 | 7 | laforge | |_. Value |_. Algorithm |_. Supported Mode | |
| 69 | |01|Milenage|2G + 3G| |
||
| 70 | |03|COMP128v1|2G| |
||
| 71 | |04|XOR 2G|2G| |
||
| 72 | |06|COMP128v2|2G| |
||
| 73 | |07|COMP128v3|2G| |
||
| 74 | |08|XOR 3G|3G| |
||
| 75 | 8 | dexter | |
| 76 | |||
| 77 | h3. Setting the Milenage parameters (Ci/Ri) |
||
| 78 | |||
| 79 | Use a standard UPATE BINARY command on EF.MLNGC (7FCC/6F01) |
||
| 80 | |||
| 81 | |_. Offset |_. Size |_. Description | |
||
| 82 | |0|16|C1| |
||
| 83 | |16|16|C2| |
||
| 84 | |32|16|C3| |
||
| 85 | |48|16|C4| |
||
| 86 | |64|16|C5| |
||
| 87 | |80|1|R1| |
||
| 88 | |81|1|R2| |
||
| 89 | |82|1|R3| |
||
| 90 | |83|1|R4| |
||
| 91 | |84|1|R5| |
