2016-12-08 16:50:03 +00:00
|
|
|
Testing OAP messages
|
|
|
|
- Register Request
|
|
|
|
encoded message:
|
|
|
|
04 30 02 23 42
|
|
|
|
ok
|
|
|
|
- Register Error
|
|
|
|
encoded message:
|
|
|
|
05 02 01 6f
|
|
|
|
ok
|
|
|
|
- Register Result
|
|
|
|
encoded message:
|
|
|
|
06
|
|
|
|
ok
|
|
|
|
- Challenge Request, no rand, no autn
|
|
|
|
encoded message:
|
|
|
|
08
|
|
|
|
ok
|
|
|
|
- Challenge Request, with rand, no autn
|
|
|
|
encoded message:
|
|
|
|
08 20 10 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10
|
|
|
|
ok
|
|
|
|
- Challenge Request, no rand, with autn
|
|
|
|
encoded message:
|
|
|
|
08 23 10 ce c4 e3 84 8a 33 00 00 86 78 11 58 ca 40 f1 36
|
|
|
|
ok
|
|
|
|
- Challenge Request, with rand, with autn
|
|
|
|
encoded message:
|
|
|
|
08 20 10 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 23 10 ce c4 e3 84 8a 33 00 00 86 78 11 58 ca 40 f1 36
|
|
|
|
ok
|
|
|
|
- Challenge Error
|
|
|
|
encoded message:
|
|
|
|
09 02 01 17
|
|
|
|
ok
|
|
|
|
- Challenge Result
|
|
|
|
encoded message:
|
|
|
|
0a 24 08 01 02 03 04 05 06 07 08
|
|
|
|
ok
|
|
|
|
- Sync Request
|
|
|
|
encoded message:
|
GSUP, OAP, osmo-gen-vec: fix AUTS length to 14, not 16
GSUP transmits AUTS for UMTS authentication procedures, and OAP uses the same
procedures to authenticate. osmo-gen-vec is a utility program that passes AUTS
to our osmo_auth_gen_vec_auts() API.
According to 3GPP 33.102 6.3.3, AUTS = SQN^AK || MAC-S, which are 6 || 8 == 14
bytes. This is confirmed by 24.008 9.2.3a where the TLV has 16 bytes, TL = 2
and AUTS being the V = 14.
It is not harmful for milenage_gen_vec_auts() to pass two more AUTS bytes. But
writing 16 bytes to a GSUP struct is a potential problem when passing in a 14
byte long AUTS buffer to the GSUP API, which then reads past the AUTS buffer.
The API implies the length, so far to be 16, so passing in a 14 byte buffer to
GSUP would require copying to a larger buffer first.
Fix this by using a length of 14 for AUTS everywhere instead.
This constitues an ABI breakage, we may handle it as a "fix before an official
release", otherwise we need a version bump.
The OAP protocol document has also been updated, needs an update in the
osmo-gsm-manuals as well.
Change-Id: If25b173d9ec57ea4c504d860954912b7d82af455
2017-02-02 19:05:14 +00:00
|
|
|
0c 25 0e 10 20 30 40 50 60 70 80 90 a0 b0 c0 d0 e0
|
2016-12-08 16:50:03 +00:00
|
|
|
ok
|
|
|
|
Done.
|