Philipp Maier
de8db1c189
In the current form we assume that the files that store the key material and the related configuration parameters have the same layout for all algorithms. This assumption makes sense since for the currently supported algorithms (not TUAK) this is indeed true. (With the exception that there may be RFU bits still set to 1, even though the spec clearly state those bits should be 0. However, this does not matter in practice) With the advent of TUAK longer keys were introduced. This made a new file layout necessary. Unfortunately this also means that we can not rely on the coincidence described above. This means we have to be more specific when reading and writing the files. This patch adds classes to model the file layout for each algorithm. We also print the key (and OP/OPc) for each location individually (2g,3g,4g5g). Even though the programmed key should be the same in all locations, this allows better diagnosis. Also with the advent of TUAK we may have different key material in 4g5g location. Related: SYS#6473 |
||
---|---|---|
.. | ||
sja2 | ||
sjs1 | ||
run-tests |