Project

General

Profile

Bug #3224

verify ciphering after UMTS AKA

Added by neels 12 months ago. Updated 6 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Iu interface
Target version:
-
Start date:
04/30/2018
Due date:
% Done:

0%

Spec Reference:

Description

Depending on whether UMTS or GSM AKA was established, ck or kc must be used as ciphering key.
In osmo-sgsn, I cannot find any bit of code that would use the UMTS ck. All I can find is:
osmo-sgsn/src/gprs/gprs_llc.c:

                if (llme->cksn != mm->auth_triplet.key_seq &&
                    mm->auth_triplet.key_seq != GSM_KEY_SEQ_INVAL) {
                        memcpy(llme->kc, mm->auth_triplet.vec.kc,
                               gprs_cipher_key_length(mm->ciph_algo));

Verify in practical tests that ciphering works with UMTS AKA.
Also verify that when the MS responds with GSM AKA to a UMTS AKA challenge, the GSM AKA key is used.
(The same issue has been solved in the MSC not too long ago.)


Related issues

Related to OsmoSGSN - Bug #3193: auth: on GERAN, must allow GSM SRES response even to UMTS AKA challengeResolved2018-04-21

Related to OsmoSGSN - Bug #2857: No automatic testing of IuPS interfaceStalled2018-01-232018-01-23

History

#1 Updated by neels 12 months ago

  • Related to Bug #3193: auth: on GERAN, must allow GSM SRES response even to UMTS AKA challenge added

#2 Updated by laforge 10 months ago

  • Related to Bug #2857: No automatic testing of IuPS interface added

#3 Updated by neels 8 months ago

  • Assignee set to lynxis

assigning to lynxis -- is this resolved by your osmo-sgsn patches?

#4 Updated by lynxis 8 months ago

no. it's not. There is still no ciphering (yet) implemented.

#5 Updated by laforge 6 days ago

  • Category set to Iu interface

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)