Project

General

Profile

Actions

Bug #3043

closed

A5/3 encryption fails

Added by jbruckner almost 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
03/08/2018
Due date:
% Done:

100%

Spec Reference:

Description

This was discussed a bit on the mailing list already: http://lists.osmocom.org/pipermail/openbsc/2018-March/011811.html

I'm attaching the Wireshark traces from the mails. Please see the respective mail from the archive for a description of what has been recorded there.

Here's my initial mail:
-------------
I’m having trouble using the A5/3 encryption in my setup. A5/1 works perfectly fine [attachment a5_1.pcapng]. As soon as I switch to A5/3 and e.g. send an SMS, the last valid message I see in the Wireshark traces of the GSMTAP of osmo-bts-trx is the Ciphering Mode Command requesting A5/3. After that, several messages arrive at the bts, but it seems like it can’t make any sense of them. The MS repeatedly tries to send the SMS but never succeeds [attachment a5_3.pcapng]. Both MSs are connected to the same bts.

According to the Classmarks of all MSs, A5/1 as well as A5/3 are supported.
This is my Setup:
- USRP N210
- osmo-trx
- osmo-bts-trx
- osmo-nitb
- osmo-pcu
- osmo-sgsn
- osmo-ggsn
I’m using a Debian 9 VM and tried both the packages from osmocom-latest as well as osmocom-nightly.
The MSs I’ve tested are two Nexus 6 and one Samsung Galaxy S I9000. All three with sysmocom nano USIMs.

Could the decryption at the bts be incorrect? Has anyone tested/used it recently?
I’ll be happy to provide additional information if needed.
-------------


Files

a5_1.pcapng a5_1.pcapng 11.4 KB http://lists.osmocom.org/pipermail/openbsc/2018-March/011811.html jbruckner, 03/08/2018 10:12 AM
a5_1_3_with_LU_Auth.pcapng a5_1_3_with_LU_Auth.pcapng 94.1 KB http://lists.osmocom.org/pipermail/openbsc/2018-March/011816.html jbruckner, 03/08/2018 10:12 AM
a5_3.pcapng a5_3.pcapng 68 KB http://lists.osmocom.org/pipermail/openbsc/2018-March/011811.html jbruckner, 03/08/2018 10:12 AM
attach_a5_0_1_3.pcapng attach_a5_0_1_3.pcapng 85.6 KB http://lists.osmocom.org/pipermail/openbsc/2018-March/011823.html jbruckner, 03/08/2018 10:12 AM
a5_3_Cipher_Mode_Reject.txt a5_3_Cipher_Mode_Reject.txt 7.1 KB jbruckner, 04/18/2018 01:14 PM

Related issues

Related to OsmoBSC - Bug #3183: BSC_Tests.ttcn lacks tests for BSSMAP Cipher Mode ControlResolvedlaforge04/18/2018

Actions
Related to OsmoBTS - Bug #3184: BTS_Tests.ttcn is lacking test for encryptionResolvedlaforge04/18/2018

Actions
Related to OsmoMSC - Bug #2947: OsmoMSC crashes with A5/3 configured and MS sending no Classmark 2 in LU RequestResolvedneels02/15/2018

Actions
Related to OsmoBSC - Bug #3186: cipher mode reject may be sent with invalid cause codeResolvedosmith04/19/2018

Actions
Related to OsmoMSC - Bug #3187: rx cipher mode reject from BSS brokenClosedmsuraev04/19/2018

Actions
Related to OsmoMSC - Feature #2795: Handle UTRAN_CLSM_CHG in MSCNewneels12/29/2017

Actions
Related to OsmoGSMTester - Feature #3563: osmo-gsm-tester: add test case: test a5/3Resolvedpespin09/18/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)