diff options
| author | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-07 15:38:59 +0100 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-03-10 19:07:38 +0100 |
| commit | 3c7656a481931f7d001119c5ec0a7b2b10bd2744 (patch) | |
| tree | 044271ae05a575e2bae82e094baf1fec7bd9812a /tests/osmo-sgsn_test-nodes.vty | |
| parent | 340a7e93394817d1e8d9cc9221475afc2029835a (diff) | |
Iu: add UEA encryption
Add vty 'encryption uea 0 1 2', defaults to 'encryption uea 0' to yield
previous behavior.
If any UEA above 0 is enabled, include the UEA key in the Iu Security
Mode Command.
I noticed that only the code bit in st_iu_security_cmd_on_enter()
affects the test. The same code in gsm48_gmm_authorize() seems to be
dead code? But applying the patch there as well just to be safe.
We cannot yet verify the chosen UEA to match a configured UEA level,
because the iu_client.c does not send us message details with the
RANAP_IU_EVENT_SECURITY_MODE_COMPLETE.
Also we cannot yet send the set of configured UEA to the hNodeB, since,
again, iu_client.c does not provide the proper API for it.
The proper solution here is to completely dissolve iu_client.c and do
all Iu handling in osmo-sgsn itself -- see OS#5487.
Related: SYS#5516
Related: I1a7c3b156830058c43f15f55883ea301d2d01d5f (osmo-ttcn3-hacks)
Change-Id: I27e8e0078c45426bf227bb44aac82a4875d18d0f
Diffstat (limited to 'tests/osmo-sgsn_test-nodes.vty')
| -rw-r--r-- | tests/osmo-sgsn_test-nodes.vty | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/osmo-sgsn_test-nodes.vty b/tests/osmo-sgsn_test-nodes.vty index f2ed2dce7..7e2e3a3f2 100644 --- a/tests/osmo-sgsn_test-nodes.vty +++ b/tests/osmo-sgsn_test-nodes.vty @@ -36,6 +36,7 @@ OsmoSGSN(config-sgsn)# list auth-policy (accept-all|closed|acl-only|remote) authentication (optional|required) encryption gea <0-4> [<0-4>] [<0-4>] [<0-4>] [<0-4>] + encryption uea <0-2> [<0-2>] [<0-2>] gsup ipa-name NAME gsup remote-ip A.B.C.D gsup remote-port <0-65535> |