Hi!
I'm now at a point where I would like to add SNOW-3G (EIA1/EEA1) support for
NAS integrity protection and ciphering to my upcoming TTCN-3 testsuite for the MME.
However, it seems there is no real FOSS implementation of the SNOW-3G algoritm
around? All I could find was:
* https://github.com/mitshell/CryptoMobile with unclear source of the code,
without a copyright statement or license annotation
* https://github.com/rcatolino/libressl-snow3g/blob/master/crypto/snow3g/main…
without a copyright statement or license annotation
* https://github.com/Jadson27101/SNOW_3G in go,
without a copyright statement or license annotation
* https://github.com/KsirbJ/SNOW-3G
without a copyright statement or license annotation
* https://github.com/open5gs/nextepc/blob/master/src/mme/snow-3g.c
without a copyright statement or license annotation. Looks rather similar
to CryptoMobile. Possible just copy+pasted from ETSI reference implementation?
* https://github.com/srsLTE/srsLTE/blob/master/lib/src/common/snow_3g.cc
also contains no coypright statement or license, but might be construed
to be AGPLv3 like all of srsLTE. However, it states it is "adapted"
from ETSI/SAGE specifications. Does that mean it is an independent
implementation of the algorithm by just reading the specs, or does it
contain actual ETSI-copyrighted code?
It's also odd that the 3GPP specs (35.215 / 35.216, with usual copyright statement)
don't contain any actual information but all just point to the ETSI SAGE specification
which can be found (at the very least) here:
https://www.gsma.com/aboutus/wp-content/uploads/2014/12/uea2uia2d1v21.pdf
and interestingly doesn't contain any copyright statement whatsoever.
This discussion is not about any potentially 'essential patents' that may or may
not apply in some jurisdictions on the algorithm itself. I'm currently only interested
in a "clean copyright" implementation of any of the EIA/EEA implementations used
on the LTE NAS layer.
I'd appreciate any useful comments. Thanks!
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear all,
I'm very happy to have received the below attached news via the Eclipse
bugzilla.
This is great, as it permits us to have "real" SI rest octet as well as
RLC/MAC support in our TTCN3 test suites while still using declarative
RAW codec syntax.
Just to be clear there's no misunderstanding: This doesn't mean that
CSN.1 syntax can be parsed by TITAN. It just means that we can use RAW
codec annotations to describe something that matches the CSN.1 encoding.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear Osmocom community,
during recent years we have developed a quite extensive set of test suites
for virtually all interfaces on all protocol levels of our 2G stack, and
recently even extended at least with some 3G IuCS coverage.
Those test suites are considerably valuable for testing any kind of
implementation of 2G / 3G network elements, even beyond Osmocom. I'm a
bit worried that they might be used to test proprietary implementations,
which would bring no value to growing FOSS in mobile communications.
Whether we license the test suites under GPL or AGPL doesn't actually
change much here: Imagine "EvilCorp" developing a BSC, using our test
suites against it. They neither distribute the test suite, nor do they
provide "access over a network" to it, an hence they could keep any
modifications/extensions/derivatives private without having to
contribute those back.
I think this is problematic. We develop those test suites because we
care about having well-tested FOSS in cellular communications, whether
Osmocom or other FOSS projects. I certainly don't want to spend my
spare time, or invest sysmocom resources towards improving the test
coverage of any non-FOSS implementations. If such users are out there,
they should at the very least contribute to the development effort in
one way (code) or another (funding).
For 2G/3G, I think this discussion is quite theoretical, as there is
unlikely anyone else implementing those old technologies in proprietary
systems - Osmocom is probably typically the latest player in the market
to do so.
However, as I'm currently working on a first set of TTCN3 tests for
testing a LTE MME (initially attacing to S1 and SGs), I'm wondering if
we should continue to release related code under traditional copyleft
licenses.
One idea would be to have a license that permits the use of the test
suites to test only FOSS software. In theory, that would mean that all
projects we care about (such as currently srsLTE, nextepc, OAI EPC, ...)
could use the test suites to test their software. On the other hand,
if some vendor of proprietary MME/EPC software would want to [legally]
use the tests, they would need to obtain a different (paid) license to
the test suite. Of course they could simply ignore the license and we'd
have little chance to learn about it - but I would argue most proper
companies typically would obtain a license if they used some software
they knew they had to license.
This is a very double-edged sword. Drafting such a new license would
cause license proliferation, which is always bad. It also raises
quesetions of license compatibility with e.g. some of our common
existing 'library' code that would need to be investigated. Finally, it
also means that we'd no longer be writing "free software" nor "open
source", as the respective relevant definitions always require "non
discriminatory use for any purpose", which would no longer be the case
here.
This is currently an early stage brainstorming. Now is the right point
in time to talk about this, before we release any LTE/EPC related tests.
Let me know if you have any thoughts to share. While I'm cross-posting
this to openbsc@ and nextepc@ lists, pleaes follow-up-to
openbsc(a)lists.osmocom.org, as that's the main Osmocom mailing list and
we don't have any specifically only for the test suites.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear ML,
I'm wondering why we do not have gsmtap logging enabled for TTCN3
testsuites, and if there are any reasons against doing that.
Personally I find it very useful to have gsmtap logs in pcap files,
because then then there is no need to manually match the timestamps of
the log file and interesting parts of the pcap dump.
Especially in the TTCN3 testsuites, where we generate a separate pcap
file for each test, but have one big log file of the SUT (e.g. osmo-hlr)
for the entire testsuite run.
Thoughts?
Thanks,
Oliver
--
- Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hi Holger,
I was planning to add osmo-pcap recipes to meta-telephony soon, and
first of all I wanted to make a new release since last tag (0.0.6)
looked quite old. But then I found in debian/changelog that actually a
lot of new releases exists, but their git tags are missing in the
osmo-pcap git repository.
So after making sure I updated my tag list from the server (gerrit). I got:
$ git tag
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.0.6
but according to git log from debian/changelog, releases 0.0.7-0.0.11 do
exist.
Interestingly, tags 0.0.5 and 0.0.6 point to the same commit.
Commits adding new releases without tags, see for instance:
a316c9394aa27d25b3d7fba004563890a43ab1bc (0.0.7 added)
fbdcf593f80d4fe5330376674136fd76fcef5ea2 (0.0.8 added
c016b5d3824923c2b35c67cfb9930a30e564f07e (0.0.9 added)
fdebd88059df3a8f717614548dcd7247e8890f9a (0.0.10 added)
17f5b005066a15312525e53e7b4a574d40011f96 (0.0.11 added)
4776b2972e84ef75b3a1c884da19604d87fc7f68 (a new commit added to 0.11
section?)
So, I want to ask if there's some explanation for those tags missing or
you simply forgot to push them when creating the releases (or they got
somehow lost in the server).
Do you happen to have the tags locally and can push them? or otherwise
generate the tags now and push them. I can also do it if you want, I'll
push tags on the commits from the list I wrote above.
BTW, in case you run into a Make error while building current master, it
may be fixed here:
https://gerrit.osmocom.org/c/osmo-pcap/+/14666
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hello,
Has anybody tested PS (either 2G or 3G) with Samsung phones?
Have you experienced any problems? (like having no internet though at
the same time PDP is active and GTP traffic is flowing in both
directions)
Kind regards,
Mykola Shchetinin
Hello.
I just followed the step by step procedure outlined in the wiki to compile
OpenBSC on Ubuntu 16.04 LTS for the ip.access nanoBTS. My problem is that
the folder ipaccess which has the ipaccess.config is missing and so is the
abisip-find file.
Any leads on why this is happening? I had seen somewhere that the above can
be found in the osmocom-ipaccess-utils from the repo but that too is
unavailable.
Many thanks
-tyrus
Hello ML,
cloning from git.osmocom.org is sporadically failing. From one CI job
that ran today:
> Cloning into 'osmo-bsc'...
> error: garbage at end of loose object 'b5511145af6213e2d23a3e9890fd42b8aaa0dc1b'
> fatal: loose object b5511145af6213e2d23a3e9890fd42b8aaa0dc1b (stored in <https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_latest/ws/osmo-bsc/.git…)> is corrupt
> Build step 'Execute shell' marked build as failure
https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_latest/628/display/redi…
Another job failed today with:
> + git -C osmo-bts fetch
> fatal: unable to access 'https://git.osmocom.org/osmo-bts/': The requested URL returned error: 504
I've restarted the CI jobs.
Regards,
Oliver
--
- Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hi Harald!
Unfortunately, your change [1] breaks some osmo-* projects.
I am getting the following segfault with OsmoMSC:
[1] https://git.osmocom.org/libosmocore/commit/?id=b3f94eb39e19366c3458643ee329…
[1] https://gerrit.osmocom.org/#/c/libosmocore/+/14361/
ERROR: osmo_log_info == NULL! You must call log_init() before using
logging in log_check_level()!
Assert failed osmo_log_info logging.c:184
backtrace() returned 10 addresses
/usr/local/lib/libosmocore.so.12(+0x16f6b) [0x7ffff72dff6b]
/usr/local/lib/libosmocore.so.12(osmo_panic+0xc0) [0x7ffff72dff20]
/usr/local/lib/libosmocore.so.12(+0x14487) [0x7ffff72dd487]
/usr/local/lib/libosmocore.so.12(log_check_level+0x1a) [0x7ffff72de82a]
/usr/local/lib/libosmocore.so.12(osmo_fsm_register+0xef) [0x7ffff72d81bf]
/home/wmn/osmocom/osmo-msc/tests/msc_vlr/msc_vlr_test_ss() [0x692e03]
/home/wmn/osmocom/osmo-msc/tests/msc_vlr/msc_vlr_test_ss() [0x9b6aad]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7ffff595fed5]
/home/wmn/osmocom/osmo-msc/tests/msc_vlr/msc_vlr_test_ss() [0x4215cc]
gdb-peda$ bt
#0 0x00007ffff5974c37 in __GI_raise (sig=sig@entry=0x6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007ffff5978028 in __GI_abort () at abort.c:89
#2 0x00007ffff72dff25 in osmo_panic_default (args=0x7fffffffda48,
fmt=0x7ffff72e8cb9 "Assert failed %s %s:%d\n") at panic.c:49
#3 osmo_panic (fmt=fmt@entry=0x7ffff72e8cb9 "Assert failed %s
%s:%d\n") at panic.c:84
#4 0x00007ffff72dd487 in assert_loginfo (src=<optimized out>) at logging.c:184
#5 0x00007ffff72de82a in log_check_level
(subsys=subsys@entry=0xffffffff, level=level@entry=0x7) at
logging.c:1033
#6 0x00007ffff72d81bf in osmo_fsm_register (fsm=0xcc6c20 <msc_a_fsm>)
at fsm.c:261
#7 0x0000000000692e03 in msc_a_fsm_init () at msc_a.c:1003
#8 0x00000000009b6aad in __libc_csu_init ()
#9 0x00007ffff595fed5 in __libc_start_main (main=0x517540 <main>,
argc=0x1, argv=0x7fffffffdcb8, init=0x9b6a60 <__libc_csu_init>,
fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=0x7fffffffdca8) at libc-start.c:246
#10 0x00000000004215cc in _start ()
As can be seen, this happens when we register 'msc_a' FSM,
which of course has .allstate_event_mask == 0x00, and dummy
.allstate_action == msc_a_fsm_allstate_action(), which
basically does nothing.
The registration happens even before the main() is called,
since we use '__attribute__((constructor))', and logging
is not yet initialized at that time.
We need to fix the FSM definition, but right now I think
we have no other way than reverting [1].
With best regards,
Vadim Yanitskiy.
Hi Pau,
today I cannot sign in to Gerrit for some magic reason,
so I would like to post some notes about your change [1].
[1] https://gerrit.osmocom.org/#/c/osmo-sgsn/+/14445/
> [...] it changed the default logic for remote policy to not require
> authentication, which broke TTCN3 tests because sgsn no longer
> tries to authenticate the users.
My bad, sorry for that.
> let's enable it by default when on auth-policy remote.
ACK.
> doc/manuals/vty/sgsn_vty_reference.xml
> Allow MS to attach via GERAN without authentication
> (default and only possible value for non-remote auth-policy)
Actually, no. My motivation for introducing this VTY parameter
was exactly the ability to use remote auth-policy (i.e. OsmoHLR)
to check if a subscriber is known, but not to require
authentication, just like we can do in CS-domain. In other words,
'authentication optional' should work with 'auth-policy remote'.
> src/gprs/sgsn_vty.c
> DEFUN(cfg_authentication, cfg_authentication_cmd,
> [...]
> Allow MS to attach via GERAN without authentication
> (default and only possible value for non-remote auth-policy)
Same here. It *is* possible for 'auth-policy remote' too.
> src/gprs/gprs_sgsn.c
> struct sgsn_instance *sgsn_instance_alloc(void *talloc_ctx)
> [...]
> inst->cfg.auth_policy = SGSN_AUTH_POLICY_CLOSED;
> /* only applies if auth_policy is REMOTE */
> inst->cfg.require_authentication = true;
> [...]
Are you sure this wouldn't break non-remote auth-policy use cases?
AFAIR, the GMM layer requests authentication regardless of the
'auth-policy', so then in 'gprs/sgsn_auth.c' we conditionally
perform authentication or immediately return SGSN_AUTH_ACCEPTED.
An alternative solution is to invert 'cfg.require_authentication',
e.g. to 'cfg.omit_authentication', so by default we will require
authentication since it's initialized to false.
With best regards,
Vadim Yanitskiy.
