Actions
Bug #3187
closedrx cipher mode reject from BSS broken
Start date:
04/19/2018
Due date:
% Done:
60%
Resolution:
Spec Reference:
Description
bssmap_rx_ciph_rej() looks for a cause IE using the BSS_MAP_MSG_CIPHER_MODE_REJECT message discriminator. This is clearly wrong and invariably leads to
<000a> a_iface_bssap.c:629 Rx MSC DT1 BSSMAP CIPHER MODE REJECT <000a> a_iface_bssap.c:453 BSC sends cipher mode reject (conn_id=65) <000a> a_iface_bssap.c:457 Cause code is missing -- discarding message!
We need a test verifying that the MSC properly receives a Cipher Mode Reject.
Since in ttcn3, we don't verify log output, this might actually be good to incorporate in the msc_vlr tests instead?
Is there a message response we could trigger on in ttcn3?
Related issues
Updated by neels about 6 years ago
- Related to Bug #3043: A5/3 encryption fails added
Updated by laforge over 5 years ago
- Category set to A interface (general)
- Assignee changed from neels to msuraev
Updated by msuraev over 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 60
Fix is available in https://gerrit.osmocom.org/#/c/osmo-msc/+/11569/ not sure how to test it yet though.
Updated by msuraev over 5 years ago
One way to test this in ttcn would be to introduce counter for cipher mode reject and check its value via CTRL interface.
Updated by msuraev over 5 years ago
Patches for libosmocore and osmo-msc were merged. Remaining bits:
- add TTCN3 tests checking related counters
Actions