mirror of https://gerrit.osmocom.org/libosmocore
Harald Welte
d8e5309527
There are 3G algorithms which support different lengths of RES values (4, 8, 16 byte). For MILENAGE, we never really had to bother, as the 4-byte RES is simply the first 4 bytes of the 8-byte RES. However, for TUAK, the expected RES length is an input parameter to the Keccak crypto functions, so the result of all parameters (including CK, IK, ...) will be completely different for RES length 4 than RES length 8. So let's permit the caller of the osmocom auth API to specify the requested RES length via the osmo_auth_vector.res_len parameter. For backwards compatibility of callers of the old osmo_auth_gen_vec/ osmo_auth_gen_vec_auts API: Always force the res_len to 8 in this case, which was the hard-coded length before this patch. Change-Id: Ic662843fbe8b5c58e4af39ea630ad5ac13fd6bef |
||
|---|---|---|
| .. | ||
| osmo-stat-dummy | ||
| Makefile.am | ||
| conv_codes_gsm.py | ||
| conv_gen.py | ||
| gen_website_doc_tree.sh | ||
| gsmtap-logsend.c | ||
| gsmtap.py | ||
| gsmtap_logread.py | ||
| osmo-aka-verify.c | ||
| osmo-arfcn.c | ||
| osmo-auc-gen.c | ||
| osmo-config-merge.c | ||
| osmo-ns-dummy-vty.c | ||
| osmo-ns-dummy.c | ||
| osmo-sim-test.c | ||