libosmocore: gsm48_mi_to_string() TMSI parsing

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/.

Вадим Яницкий axilirator at gmail.com
Wed Mar 16 15:26:57 UTC 2016


Hello, Harald!

There are two patches. One for libosmocore, another one for OpenBSC
(sorry for a little bit of mess). Right now I have no opportunity to test
it, but
the output of 'make check' seems ok.

С наилучшими пожеланиями,
Яницкий Вадим.

2016-03-16 16:22 GMT+06:00 Harald Welte <laforge at gnumonks.org>:

> Hi Vadim,
>
> On Tue, Mar 15, 2016 at 01:46:31AM +0600, Вадим Яницкий wrote:
> > I found that it is used in several projects like OsmocomBB and OpenBSC,
> > but it seems a bit strange to me that the TMSI represented in decimal...
>
> yes, indeed this seems highly unusual.  It reflects on the fact how
> little we knew about the usual representation of TMSIs back when we
> started to write that code.
>
> > Can we move to use a hex representation instead of decimal? And why if
> not?
>
> yes, I would merge an associated patch.  Preferrably together with
> patches for other locations where we print an IMSI and use the decimal
> representation at this point.
>
> --
> - 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)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160316/b9110b97/attachment.htm>


More information about the OpenBSC mailing list