OsmoBTS doesn't reject RSL CHAN ACT for unsupported ciphers
When using an unsupported cipher, the RSL CHAN ACT should result in a RSL CHAN ACT NACK due to the unsupported cipher.
However, OsmoBTS instead simply acknowledges the channel activation and activates the channel with A5/0. This is actually the underlying cause of #3253
#2 Updated by laforge over 2 years ago
- % Done changed from 0 to 30
The problem is
encr_info2lchan() which uses
bts_supports_cipher() to determine if the cipher is suppored. However, if
bts_supports_cipher() returns 0 (not supported), it uses this value as return value of
encr_info2lchan() where '0' means success (standard osmocom convention). This results in channel activation proceeding, which it shouldn't.