This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
dexter zero-kelvin at gmx.de-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Sébastien > However, I known nothing to the GSM protocol and don't understand why the Kc > must be saved. This value is generated from the RUN GSM ALGORITHM command, > isn't it? According to the spec, is the ME supposed to backup the last > computed key or something like that? No idea, but they backup a lot stuff, like last used ARFCNs and so on. > However, I cannot find a file for the famous "cannot be read" Ki used as > input to the RUN GSM ALG command. Is this key not stored in a SIM file? Not > documented in the spec? I think I will do that even if not specified. I think it is stored in a file, but the read access will be disabled, but you are right, the spec does not specify an EF:KI or anything semilar. You could try to select all files 0000 to FFFF maybe you find something undocumentated ;-) > "stored in the SIM" means nothing special, so what's not forbidden is > allowed. Ki will be in a file too. Does someone see a problem with this? No, that should be absolutely no problem - no phone will ever do a select to this file ;-) Regards. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuetBsACgkQrQQa6thSCbBhPgCgmZWnxAtRdt7hIb2AdCQvZqKJ 9IAAn2HsZuGdwBNGHqVbSSmUbZsddd/h =+mzg -----END PGP SIGNATURE-----