<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<pre style="white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">Hi Harald,
The srsLTE implementation is taken from the ETSI specs simulation program listings: <a href="http://cryptome.org/uea2-uia2/etsi_sage_06_09_06.pdf">http://cryptome.org/uea2-uia2/etsi_sage_06_09_06.pdf</a> and <a href="http://cryptome.org/uea2-uia2/snow_3g_spec.pdf">http://cryptome.org/uea2-uia2/snow_3g_spec.pdf</a>
<a href="https://www.etsi.org/intellectual-property-rights#mytoc3">https://www.etsi.org/intellectual-property-rights#mytoc3</a> and <a href="https://www.etsi.org/images/files/IPR/etsi-ipr-policy.pdf">https://www.etsi.org/images/files/IPR/etsi-ipr-policy.pdf</a> outline the copyright licensing details for software incorporated in ETSI standards however I have not taken legal advice on compatibility of this license with AGPLv3.
>From a quick review, it looks like the CryptoMobile and NextEPC versions have taken the same approach.
It would be good as you say to have a "clean copyright" implementation - perhaps this is something we could help with.
Best regards,
Paul
<blockquote type="cite"><pre style="white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">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:
* <a href="https://github.com/mitshell/CryptoMobile">https://github.com/mitshell/CryptoMobile</a> with unclear source of the code,
without a copyright statement or license annotation
* <a href="https://github.com/rcatolino/libressl-snow3g/blob/master/crypto/snow3g/main.c">https://github.com/rcatolino/libressl-snow3g/blob/master/crypto/snow3g/main.c</a>
without a copyright statement or license annotation
* <a href="https://github.com/Jadson27101/SNOW_3G">https://github.com/Jadson27101/SNOW_3G</a> in go,
without a copyright statement or license annotation
* <a href="https://github.com/KsirbJ/SNOW-3G">https://github.com/KsirbJ/SNOW-3G</a>
without a copyright statement or license annotation
* <a href="https://github.com/open5gs/nextepc/blob/master/src/mme/snow-3g.c">https://github.com/open5gs/nextepc/blob/master/src/mme/snow-3g.c</a>
without a copyright statement or license annotation. Looks rather similar
to CryptoMobile. Possible just copy+pasted from ETSI reference implementation?
* <a href="https://github.com/srsLTE/srsLTE/blob/master/lib/src/common/snow_3g.cc">https://github.com/srsLTE/srsLTE/blob/master/lib/src/common/snow_3g.cc</a>
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:
<a href="https://www.gsma.com/aboutus/wp-content/uploads/2014/12/uea2uia2d1v21.pdf">https://www.gsma.com/aboutus/wp-content/uploads/2014/12/uea2uia2d1v21.pdf</a>
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 <<a href="https://lists.osmocom.org/mailman/listinfo/openbsc">laforge at gnumonks.org</a>> <a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)</pre>
</blockquote>
</pre>
<pre class="moz-signature" cols="72">--
________________________________________________________________
Paul Sutton Ph.D.
Software Radio Systems (SRS)
<a class="moz-txt-link-freetext" href="http://www.softwareradiosystems.com">http://www.softwareradiosystems.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:paul@softwareradiosystems.com">paul@softwareradiosystems.com</a>
PGP Key ID: 3B4A5292
Fingerprint: B0AC 19C9 B228 A6EB 86E1 82B2 90C7 EC95 3B4A 5292
________________________________________________________________
</pre>
</body>
</html>