Actions
Bug #3224
openverify ciphering after UMTS AKA
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
Updated by neels almost 6 years ago
- Related to Bug #3193: auth: on GERAN, must allow GSM SRES response even to UMTS AKA challenge added
Updated by laforge over 5 years ago
- Related to Bug #2857: No automatic testing of IuPS interface added
Updated by neels over 5 years ago
- Assignee set to lynxis
assigning to lynxis -- is this resolved by your osmo-sgsn patches?
Actions