Bug #3254
closed
OsmoBTS doesn't reject RSL CHAN ACT for unsupported ciphers
Added by laforge almost 6 years ago.
Updated almost 6 years ago.
Description
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
- Related to Bug #3253: osmo-bts-trx doesn't enable A5/3 added
- % 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.
- Status changed from New to In Progress
- % Done changed from 30 to 80
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Also available in: Atom
PDF
