LegalAspects » History » Version 3
laforge, 02/19/2016 10:48 PM
1 | 2 | laforge | [[PageOutline]] |
---|---|---|---|
2 | 1 | laforge | = Legal Aspects = |
3 | |||
4 | This page documents our position on legal aspects of the project. |
||
5 | |||
6 | Since there is a lot of uncertainty and confusion regarding the legality of any independent open source work in GSM, |
||
7 | we explicitly state that this is a legitimate project. |
||
8 | |||
9 | * We do not infringe on any copyright |
||
10 | * We do not reveal any trade secrets |
||
11 | * We do not break any digital restrictions (DRM) |
||
12 | * We do not implement or break any encryption algorithm |
||
13 | |||
14 | == Copyright == |
||
15 | |||
16 | This project honors the copyright of third parties. |
||
17 | |||
18 | Specifically, the source code published by us does not infringe on copyrights of others like Motorola, TI, Vitelcom or Compal. |
||
19 | |||
20 | The software we publish for the GSM baseband is either original development by the project engineers or source code that is taken from sources licensed under GNU GPL. |
||
21 | |||
22 | == Information Sources == |
||
23 | |||
24 | We outline that we have only used public sources of information in the development of this project. There is no infringement on trade secrets of any sort. |
||
25 | |||
26 | === Documentation on the GSM protocols === |
||
27 | |||
28 | The GSM protocols are fully documented and specified by the 3GPP. They are publicly available for everyone. |
||
29 | There are no trade secrets involved in imlpementing the GSM protocols, including the Um air interface betwee phone and network. |
||
30 | |||
31 | The only parts that are undisclosed are the optional encryption methods called A5. Despite their secrecy, they have been thoroughly documented and broken in |
||
32 | academic research and resulting publications. There is no trade secret in that encryption anymore. |
||
33 | |||
34 | Furthermore, in those phones that our software runs on, the A5 encryption is implemented as a black box in hardware. Our software contains no information |
||
35 | about the GSM A5 encryption at all. |
||
36 | |||
37 | === Documentation on Phones === |
||
38 | |||
39 | Service Manuals including circuit descriptions and full schematics are widely available for all major phones, including the Motorola phones that we started this project on. |
||
40 | |||
41 | Such service manuals are authored by the phone maker and distributed to cellphone repair shops around the world. They are intended to aid understanding the phone hardware. |
||
42 | |||
43 | There are dozens of web sites in various countries around the world that make those schematics available. There is no serious attempt by any phone maker we know of to |
||
44 | halt the unofficial circulation of service manuals. |
||
45 | |||
46 | We officially buy the respective phones, and we wish to simply make our own software interoperable with the hardware. |
||
47 | |||
48 | === The Vitelcom TSM30 source code === |
||
49 | |||
50 | In 2005, the complete source code of the software running on the Vitelcom TSM30 phone was uploaded to the popular open source sourceforge.net website, from where it is publicly |
||
51 | availalbe for download. According to sourceforge.net statistics, it has been downloaded thousands of times ever since. As the download was never removed and no action has |
||
52 | been taken by the copyright holders, we assume that the source code was legitimately published, but under a non-permissive license. We do not use any of that copyrighted |
||
53 | code in our software, and we do not distribute that source code. We therefore do not infringe its copyright. |
||
54 | |||
55 | Even if its publication was unauthorized, its public availability for five years clearly outlines that any information contained in it can no longer be considered a trade |
||
56 | secret. Therfore, any information we deducted form it about how the digital baseband hardware works is not a trade secret either. |
||
57 | |||
58 | === The leaked Ti Calypso documentation === |
||
59 | |||
60 | At various places on the internet, two documents with register-level details on the TI Calypso DBB circuit have been published. While those documents contain notices |
||
61 | of confidentiality, their availability online once again indicates that the information contained in the documents is no secret, at least not ever since somebody might |
||
62 | have broken an NDA and publicly disclosed the information. |
||
63 | |||
64 | == Using modified phones on carrier networks == |
||
65 | |||
66 | 3 | laforge | Note: ''So far'', our custom software '''does not activate the transmitter''' in the phone. Therefore, it works in receive-only mode as of now. |
67 | 1 | laforge | |
68 | There are many reasons why we do not recommend or endorse operating our software on carrier networks |
||
69 | * the software modifies the RF parameters of the phone, which are part of the regulatory approval |
||
70 | * regulatory approval of the phones is lost once our software is installed |
||
71 | * operating equipment without regulatory approval is illegal in probably almost all jurisdictions |
||
72 | * our software is in early development stage, and while we keep our best effort, we never |
||
73 | * the terms and conditions of carrier networks vary, but will likely not allow the use of uncertified/unauthorized phones |
||
74 | |||
75 | We therefore only use our software with our own GSM test networks, e.g. using OpenBTS or OpenBSC with BS-11 or nanoBTS. |
||
76 | |||
77 | 3 | laforge | '''DO NOT USE OUR SOFTWARE ON NETWORKS WHERE YOU DO NOT HAVE EXPLICIT PERMISSION TO DO SO!''' |