[PATCH] move to hex TMSI representation

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Thu Mar 17 13:43:35 UTC 2016


Hi Holger,

On Thu, Mar 17, 2016 at 02:29:33PM +0100, Holger Freyther wrote:
> I think it was a bit too quick. I foresee one problem. Let's assume
> someone is using TMSIs and now upgrade the sourcecode. All CM Service
> Requests will fail because the TMSI is not known. What is the
> migration/mitigation plan?

ugh.  I failed to see that for some strange reason we store the TMSI as
"TEXT" in the database.  That's really odd, especailly as we use %u
formatting when searching for TMSIs in the database.

> * I think the above hunk should be reverted

done.

> * a DB schema upgrade and store the TMSI as uint32_t

correct.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list