A5/2 + A5/3 support in osmo-bsc
Right now bssmap_handle_cipher_mode() is limited in that it only supports A5/1. This limits the capabilities, as some BTSs as well as OsmoNITB do actually support A5/2 and A5/3, too.
A generic implementation that doesn't introduce restrictions would be the best solution.
#5 Updated by laforge about 1 year ago
- Status changed from New to Closed
- Assignee set to laforge
- % Done changed from 0 to 100
osmo-bsc by now supports a5/2 or a5/3. However, only one of the codecs can be permitted at any given point in time, which is quite strange and an artefact of the libcommon-cs "network" vty node parsing history :/
See #2461 for a follow-up to remove that restriction.