From 7e0c5f09e0088c0a9743ec431e068b6b600f0a2f Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Wed, 4 Jul 2012 21:37:56 +0200 Subject: BSC VTY: Allow encryption to be set to A5/3 We are currently not checking if the BTS actually suports that cipher, and we particularly don't have any hack for ip.access which apparently seems to re-use the RSL algorithm identifier for A5/2. --- openbsc/src/libbsc/bsc_vty.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/openbsc/src/libbsc/bsc_vty.c b/openbsc/src/libbsc/bsc_vty.c index 413eac44d..6948fc8a8 100644 --- a/openbsc/src/libbsc/bsc_vty.c +++ b/openbsc/src/libbsc/bsc_vty.c @@ -1173,10 +1173,11 @@ DEFUN(cfg_net_reject_cause, DEFUN(cfg_net_encryption, cfg_net_encryption_cmd, - "encryption a5 (0|1|2)", + "encryption a5 (0|1|2|3)", "Encryption options\n" "A5 encryption\n" "A5/0: No encryption\n" - "A5/1: Encryption\n" "A5/2: Export-grade Encryption\n") + "A5/1: Encryption\n" "A5/2: Export-grade Encryption\n" + "A5/3: 'New' Secure Encryption\n") { struct gsm_network *gsmnet = gsmnet_from_vty(vty); -- cgit v1.2.3