Actions
Bug #2758
closedauth algos are encoded wrongly
Start date:
12/14/2017
Due date:
% Done:
100%
Spec Reference:
Description
osmo_hlr.py lists
AUTH_ALGO_NONE = 0 AUTH_ALGO_XOR = 1 AUTH_ALGO_COMP128v1 = 2
but it should be like libosmocore/include/osmocom/crypt/auth.h:
enum osmo_auth_algo { OSMO_AUTH_ALG_NONE, OSMO_AUTH_ALG_COMP128v1, OSMO_AUTH_ALG_COMP128v2, OSMO_AUTH_ALG_COMP128v3, OSMO_AUTH_ALG_XOR, OSMO_AUTH_ALG_MILENAGE, _OSMO_AUTH_ALG_NUM, };
(we should enter subscribers by CTRL rather than direct SQL, which should abstract this away, but which we don't have commands for yet.)
The SIM cards are probably all actually using COMP128v1 all the while, yet their config suggests XOR. XOR cannot possibly work because libosmocore doesn't support it, which is why this caught my attention, and which explains that no-one took those sim cards and programmed them to XOR. I wondered about that for a long time.
Setting to urgent since it should be quick to adjust.
Updated by neels over 6 years ago
- Status changed from New to In Progress
- Assignee changed from 55360 to neels
Updated by neels over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Actions