Neels Hofmeyr 63b246453b gsup: indicate CN-Domain in SendAuthInfo Requests ... In order for osmo-hlr to be able to 100% guarantee distinct INDs for CS and PS, set CN-Domain = CS in all SendAuthInfo Requests. In Milenage auth, it is highly desirable that osmo-hlr guarantees use of distinct INDs for CS and PS domains. If an MSC and SGSN attached at the same time use the same IND bucket to generate Milenage SQN, that collision would rapidly waste SQNs and load osmo-hlr with requesting new auth tuples on each CS/PS Complete-Layer3. So far, osmo-msc did not indicate the CN domain in the GSUP SendAuthInfo Request, which was neither required nor evaluated. The CN-Domain is only sent for the UpdateLocation Request that usually follows later. Related: OS#4318 Change-Id: I22f44068268e62801cadbf6542efaf153423cd65		2019-12-12 02:10:06 +01:00
..
libmsc	libmsc: fix potential NULL-pointer dereferences detected by GCC's LTO	2019-12-02 08:44:53 +00:00
libvlr	gsup: indicate CN-Domain in SendAuthInfo Requests	2019-12-12 02:10:06 +01:00
osmo-msc	msc: exit(2) on unsupported positional arguments on command line	2019-12-03 22:19:32 +01:00
utils	configure.ac: drop useless SQLite3 dependency	2019-04-25 21:23:35 +02:00
Makefile.am	Remove local libgsupclient; Use libosmo-gsup-client from osmo-hlr	2018-08-05 11:20:21 +02:00