diff options
| author | Harald Welte <laforge@gnumonks.org> | 2012-07-04 21:37:56 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2012-07-04 21:39:27 +0200 |
| commit | ad66a2d1508d33f4c453f6d7720223667e67e4a0 (patch) | |
| tree | ba486c91eda4bc2b3915355c0e36fdaf870ab60c /openbsc/src/libbsc/bsc_vty.c | |
| parent | f383aa11a5f87ca54b693196e6d4f6df6a41b57c (diff) | |
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.
Diffstat (limited to 'openbsc/src/libbsc/bsc_vty.c')
| -rw-r--r-- | openbsc/src/libbsc/bsc_vty.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/openbsc/src/libbsc/bsc_vty.c b/openbsc/src/libbsc/bsc_vty.c index f30648824..b38b08e1f 100644 --- a/openbsc/src/libbsc/bsc_vty.c +++ b/openbsc/src/libbsc/bsc_vty.c @@ -1174,10 +1174,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); |