OpenBSC RTP / MNCC integration

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
Sat Oct 31 09:31:23 UTC 2009


Hi Andreas,

On Fri, Oct 30, 2009 at 01:29:36PM +0100, Andreas.Eversberg wrote:

> in order to remove md5 code, you can use a simple XOR to mix the input
> data.  i think it is good enough to not select the same random number as the
> base station.

I think we could use the random() / srandom() functions, which are standard
POSIX API.  We could seed it with something like the time it takes us to
receive the first location update request after boot, or something unpredictable
like that.

In the end, we have at least three parts in our system that need a 32bit random
value: The TMSI, P-TMSI and the RTP source ID 

Regards,
	Harald
-- 
- 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