Hi
i.e. when you set the a3a8_key in the hlr.sqlite3 to 01010101010101010101010101010101 the value being processed as key in the a3a8_comp128 algorithm is 02020202020202020202020202020202.
That's not a bug per-se. I think you're assuming the binary value stored in the field is used as key. This is _not_ the case. libdbi has some special binary escaping that results in the binary value stored not being the "raw" key.
Oh yay. Thanks for pointing this out.
I had to implement it for pysim (since we support updating HLR db directly from it), you can see the python code here :
http://cgit.osmocom.org/cgit/pysim/tree/ccc-gen.py?h=ccc#n33
Cheers,
Sylvain