Re: [Openbts-discuss] OpenBTS-UMTS autch and ciphering failure

[Sipos C. <sip...@kv...>]

I forgot one more thing:

OpenLTE has a Milenage authentication and ciphering implementation known to work. Maybe it worth to take a look.

Most of the implementation can be found in this file:

https://sourceforge.net/p/openlte/code/ci/master/tree/LTE_fdd_enodeb/src/LTE_fdd_enb_mme.cc

Regards,
Csaba

----- Eredeti üzenet -----
Feladó: "Tom Tsou" <to...@ts...>
Címzett: "Sipos Csaba" <sip...@kv...>
Másolatot kap: "Michael Iedema" <mic...@ra...>, "OpenBTS Discuss" <ope...@li...>
Elküldött üzenetek: Csütörtök, 2015. Január. 22. 21:41:29
Tárgy: Re: [Openbts-discuss] OpenBTS-UMTS autch and ciphering failure

On Tue, Jan 6, 2015 at 7:41 AM, Sipos Csaba
<sip...@kv...> wrote:
> Note that the "a3_a8" column which is the last one in the above exmpale is "0". I don't know if I need to set it and if yes, what souhld be the value, maybe this is the problem, maybe not.

Set the a3_a8 field to the full path for the comp128 implementation -
normally /OpenBTS/comp128.

The value string of the a3_a8 field is executed directly with Ki and
RAND as first and second arguments respectively. Check the
sipauthserve log and make sure it is not throwing an a3_a8 error for
NULL column or anything else. Otherwise Kc won't be generated.

> At this point I must ask: is there anybody here who actually passed the auth part of OpenBTS-UMTS?

My setup gets past authentication, but doesn't move past ciphering and
integrity protection. The Security Mode Command is the last RRC
message before the connection breaks and eventually restarts.

Trimmed log follows:

SGSN:Received AuthenticationAndCipheringResp message  UE#1
SGSN: waiting for registration on IMSI: 001010123456789
Register: user IMSI001010123456789 state Null 0 callID 1398185509
addCall: creating SIP message FIFO callID 1398185509
write: write REGISTER sip:127.0.0.1 SIP/2.0#015
drive: read SIP/2.0 200 OK#015
drive: osip_message_init 0
drive: osip_message_parse 0
drive: storing kc in TMSI table
Register: received status 200 OK
Register: REGISTER success
sgsnStartIntegrityProtection: Looking up Kc for imsi 001010123456789
AlgorithmF9: MAC: 121 43 15 217 3641650041
asnLogMsg: DL_DCCH RRC Security Mode Command message size=15 UE#1 URNTI=55c7

  -TT