Harald Welte 71c51df07d Shift ciphering algorithm selection from VLR to MSC ... The VLR code seems to have the assumption that there is one particular algorithm to be used, as opposed to one of a set of algorithms. What's missing is basically to decide when/where to pick the best algorithm within the capabilities of the phone (classmark) and the network configuration (net->a5_encryption_mask). So far, libvlr has no notion of classmark. Rather, libmsc has. Why does the VLR care about the particular algorithm at all? The VLR should probably simply decide if it should use encryption or not, and if so, the MSC will figure which algorithm to use. Change-Id: I5ed80ca2086560a5975a758ec568a034a9a8ab89		2018-01-28 00:09:41 +00:00
..
libcommon	debug: Remove dead log categories	2018-01-25 00:38:11 +01:00
libcommon-cs	remove dead header files bsc_msc.h, bsc_msc_data.h and bsc_rll.h	2018-01-25 00:38:06 +01:00
libmsc	Shift ciphering algorithm selection from VLR to MSC	2018-01-28 00:09:41 +00:00
libvlr	Shift ciphering algorithm selection from VLR to MSC	2018-01-28 00:09:41 +00:00
osmo-msc	debug: Remove dead log categories	2018-01-25 00:38:11 +01:00
utils	Remove utils imported from openbsc, fix building remaining util smpp_mirror	2017-12-05 19:16:32 +00:00
Makefile.am	split off osmo-msc: remove files, apply build, rename	2017-08-29 12:51:19 +00:00