Project

General

Profile

Bug #75

A5/2 + A5/3 support in osmo-bsc

Added by laforge over 2 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Spec Reference:

Description

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.


Related issues

Related to OsmoBSC - Feature #2461: Improve "encryption" VTY parameterResolved2017-08-24

History

#1 Updated by laforge over 2 years ago

  • Project changed from OpenBSC to OsmoBSC
  • Category deleted (OpenBSC)
  • Assignee deleted (laforge)

#2 Updated by laforge over 2 years ago

  • Priority changed from High to Normal

#3 Updated by laforge over 2 years ago

  • Priority changed from Normal to Low

#4 Updated by laforge 7 months ago

  • Related to Feature #2461: Improve "encryption" VTY parameter added

#5 Updated by laforge 7 months 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.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)