Neels Hofmeyr ee392bb3b1 fix debug log: adjust to new SQN increment scheme ... We can no longer accurately print the SQN from AUTS resync, since the SQN is incremented after AUTS. Instead, always print the SQN from the generated tuple, i.e. exactly the one left in auth data *after* the tuple was generated. This change was forgotten in recent adjustments to the new SQN incrementing scheme from libosmocore, in change-id I4ec5a578537acb1d9e1ebfe00a72417fc3ca5894 for libosmocore change-id Iadf43f21e0605e9e85f7e8026c40985f7ceff1a3. It should have been obvious that something was missing in the previous patch from the auc_test output: the SQN in the output changed while the AUTN remained the same. That slipped by without being noticed :/ Change-Id: I0e1e828da931a3d22c75306c55bdb7f44df6512f		2017-03-16 05:46:40 +01:00
..
gen_ts_55_205_test_sets	auc tests: fix after SQN scheme changes from libosmocore	2017-03-15 03:39:04 +01:00
Makefile.am	auc tests: adjust cosmetically to prepare for SQN changes	2017-03-15 03:38:45 +01:00
auc_test.c	auc tests: fix after SQN scheme changes from libosmocore	2017-03-15 03:39:04 +01:00
auc_test.err	fix debug log: adjust to new SQN increment scheme	2017-03-16 05:46:40 +01:00
auc_test.ok	cosmetic: rename auc_3g_test.c to auc_test.c	2017-02-22 03:25:30 +01:00
auc_ts_55_205_test_sets.err	fix debug log: adjust to new SQN increment scheme	2017-03-16 05:46:40 +01:00
auc_ts_55_205_test_sets.ok	auth: verify test sets from 3GPP TS 55.205	2017-02-01 14:22:40 +01:00