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/OpenBSC@lists.osmocom.org/.
Sylvain Munaut 246tnt at gmail.comHi, Ok, I've finished what I wanted to do before a possible merge. It now supports Kc re-use and XOR algorithm. Missing things (KnownTuples / MT-Calls encryption) should be pluggable easily afterwards without core code change. I think it'd be good if someone else could confirm it works as expected tough. To test: * Enable encryption in openbsc.cfg : network encryption a5 1 * Put some Ki. (Currently either xor or comp128v1 sims, KnownTuples not supported yet). Easy to do with the VTY interface. openbsc> enable openbsc# subscriber imsi 001010123456789 a3a8 comp128v1 5e4ab35891375d2aee812e67c309a629 > Great. As zecke can probably consider possible BSC/MSC merge fallout > from all of this, I will lean back and let him decide if/how to merge > your encryption branch. Zecke: hope this is fine with you. Zecke: Ok, I think you can have a look at the current code. It shouldn't have any impact on BSC/MSC split. The impact will come later to support MT-calls encryption but I'll wait for your subscr_get_channel modifs to be done before I look at this. Cheers, Sylvain