Bug #4095
closed
osmo_get_rand_id() can fail under debian jessie
Added by lynxis almost 5 years ago.
Updated over 3 years ago.
Description
When using debian jessie together with libosmocore and osmo-msc, osmo-msc rejects location updates because of a failing osmo_get_rand_id().
I've used an APU to produce this bug
Please reproduce/test with debian jessie (as vm, not container, because the kernel version can have a part in this bug).
And ensure the fall-back is working
- Assignee set to osmith
- Priority changed from Normal to High
- Assignee changed from osmith to roh
roh, please try to reproduce this. If it can be reproduced, we can pass that reproducing setup to one of the developers to fix it, as needed.
not sure how to properly reproduce this:
i have tried:
whats the expected failure mode? the syscall failing? or the gnutls call?
this looks fine to me:
roh@debian:~/OS4095/libosmocore$ utils/osmo-auc-gen -3 -a COMP128v2
osmo-auc-gen (C) 2011-2012 by Harald Welte
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
RAND: d9702f3518e38b014eda14e8f170d6e3
SRES: a17ca8aa
Kc: d31ddcb0c5679000
SQN: 0
IND: 0
- Status changed from New to Feedback
- Assignee changed from roh to lynxis
please submit more details how to reproduce - tnx
- Status changed from Feedback to Rejected
I don't have any jessie apu left.
I'll reject it.
Also available in: Atom
PDF
