LegalAspects » History » Version 5
laforge, 02/19/2016 10:49 PM
fix broken sentence
1 | 5 | laforge | {{>toc}} |
---|---|---|---|
2 | 1 | laforge | |
3 | 5 | laforge | h1. Legal Aspects |
4 | |||
5 | |||
6 | 1 | laforge | This page documents our position on legal aspects of the project. |
7 | |||
8 | Since there is a lot of uncertainty and confusion regarding the legality of any independent open source work in GSM, |
||
9 | we explicitly state that this is a legitimate project. |
||
10 | |||
11 | 5 | laforge | * We do not infringe on any copyright |
12 | * We do not reveal any trade secrets |
||
13 | * We do not break any digital restrictions (DRM) |
||
14 | * We do not implement or break any encryption algorithm |
||
15 | 1 | laforge | |
16 | |||
17 | 5 | laforge | h2. Copyright |
18 | |||
19 | |||
20 | 1 | laforge | This project honors the copyright of third parties. |
21 | |||
22 | Specifically, the source code published by us does not infringe on copyrights of others like Motorola, TI, Vitelcom or Compal. |
||
23 | |||
24 | 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. |
||
25 | |||
26 | |||
27 | 5 | laforge | h2. Information Sources |
28 | |||
29 | |||
30 | 1 | laforge | 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. |
31 | |||
32 | |||
33 | 5 | laforge | h3. Documentation on the GSM protocols |
34 | |||
35 | |||
36 | 1 | laforge | The GSM protocols are fully documented and specified by the 3GPP. They are publicly available for everyone. |
37 | There are no trade secrets involved in imlpementing the GSM protocols, including the Um air interface betwee phone and network. |
||
38 | |||
39 | The only parts that are undisclosed are the optional encryption methods called A5. Despite their secrecy, they have been thoroughly documented and broken in |
||
40 | academic research and resulting publications. There is no trade secret in that encryption anymore. |
||
41 | |||
42 | 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 |
||
43 | about the GSM A5 encryption at all. |
||
44 | |||
45 | |||
46 | 5 | laforge | h3. Documentation on Phones |
47 | |||
48 | |||
49 | 1 | laforge | 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. |
50 | |||
51 | 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. |
||
52 | |||
53 | 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 |
||
54 | halt the unofficial circulation of service manuals. |
||
55 | |||
56 | We officially buy the respective phones, and we wish to simply make our own software interoperable with the hardware. |
||
57 | |||
58 | |||
59 | 5 | laforge | h3. The Vitelcom TSM30 source code |
60 | |||
61 | |||
62 | 1 | laforge | 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 |
63 | 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 |
||
64 | 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 |
||
65 | code in our software, and we do not distribute that source code. We therefore do not infringe its copyright. |
||
66 | |||
67 | 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 |
||
68 | secret. Therfore, any information we deducted form it about how the digital baseband hardware works is not a trade secret either. |
||
69 | |||
70 | |||
71 | 5 | laforge | h3. The leaked Ti Calypso documentation |
72 | |||
73 | |||
74 | 1 | laforge | 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 |
75 | 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 |
||
76 | have broken an NDA and publicly disclosed the information. |
||
77 | |||
78 | |||
79 | 5 | laforge | h2. Using modified phones on carrier networks |
80 | 1 | laforge | |
81 | 5 | laforge | |
82 | Note: _So far_, our custom software *does not activate the transmitter* in the phone. Therefore, it works in receive-only mode as of now. |
||
83 | |||
84 | 1 | laforge | There are many reasons why we do not recommend or endorse operating our software on carrier networks |
85 | 5 | laforge | * the software modifies the RF parameters of the phone, which are part of the regulatory approval |
86 | ** regulatory approval of the phones is lost once our software is installed |
||
87 | ** operating equipment without regulatory approval is illegal in probably almost all jurisdictions |
||
88 | * our software is in early development stage |
||
89 | * the terms and conditions of carrier networks vary, but will likely not allow the use of uncertified/unauthorized phones |
||
90 | 3 | laforge | |
91 | 5 | laforge | We therefore only use our software with our own GSM test networks, e.g. using [[OpenBTS]] or [[OpenBSC]] with BS-11 or nanoBTS. |
92 | 1 | laforge | |
93 | 5 | laforge | *DO NOT USE OUR SOFTWARE ON NETWORKS WHERE YOU DO NOT HAVE EXPLICIT PERMISSION TO DO SO!* |