Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

radiodirective.en.xhtml 11KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <title>EU Radio Lockdown Directive - FSFE</title>
  5. <meta name="description" content="The EU Radio Lockdown Directive threatens Free Software, user rights, innovation, security, and fair competition. We can change that - join us!" />
  6. <meta name="keywords" content="radio equipment directive, RED, 2014 53 EU, radio lockdown directive, european parliament, european commission, regulation, law, lobby, policy, threat, freifunk, routers, signal" />
  7. </head>
  8. <body id="radiodirective" class="article" microformats="h-entry">
  9. <!-- Breadcumb -->
  10. <p id="category"><a href="/work.html">Our work</a></p>
  11. <!-- / Breadcumb -->
  12. <h1 class="p-name">EU Radio Lockdown Directive</h1>
  13. <div class="e-content">
  14. <div id="introduction">
  15. <p>An EU regulation may make it impossible to install a custom piece of software on most radio decives like WiFi routers, smartphones, and embedded devices. It requires hardware manufacturers to implement a barrier that disallows users to install any software which has not been certified by them. This has negative implications on user rights and Free Software, security, fair competition, the environment, and charitable community initiatives.</p>
  16. </div>
  17. <div class="right" style="max-width: 506px; width: 30%;">
  18. <img src="img/radiolockdown-cage.jpg" alt="a bird cage with a router and a mobile phone imprisoned, both sending radio waves" />
  19. </div>
  20. <p>The origin of these issues lies in one article of the <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0053">Radio Equipment Directive</a> (2014/53/EU) which has been passed in 2014. Although the directive is already implemented in the member states' national legislations, the problematic Article 3(3)(i) is still on hold and subject to exact definition.
  21. </p>
  22. <blockquote><p>[R]adio equipment [shall support] certain features in order to ensure that software can only be loaded into the radio equipment where the compliance of the combination of the radio equipment and software has been demonstrated.<br /> – <em>Radio Equipment Directive, Article 3(3)(i)</em></p></blockquote>
  23. <p>The said article requires that device manufacturers check every software which can be loaded onto the device regarding its compliance with applicable radio regulations (e.g. signal frequency and strength). Until now, the responsibility for compliance lay with users if they modified something, no matter if it was related to hardware or software. This shift of responsibility sounds convenient for users but in fact takes away the ability to control this important technology. It gives the device manfacturers the control over the choice of software which can run on their devices.</p>
  24. <p>Since 2015, the FSFE has been working on raising awareness among the public, industry, and political decision-takers, and contributes expertise to limit the negative outcomes of this article. Many organisations and companies signed our <a href="/activities/radiodirective/statement.html">Joint Statement against Radio Lockdown</a> in which we have formulated several proposals to EU institutions and EU member states with concrete steps to solve these issues.</p>
  25. <h2 id="devices">Which devices are affected?</h2>
  26. <p>By default, almost all devices which can send and receive radio signals fall under this directive. For instance, WiFi routers, mobile phones, bluetooth chips in computers, GPS receivers, and so-called "smart devices" in households. But the European Parliament asked the European Commission to adopt a so-called Delegated Act in which they define the classes of devices which shall fall under this regulation.</p>
  27. <p>In turn, the European Commission has installed an <a href="http://ec.europa.eu/transparency/regexpert/index.cfm?do=groupDetail.groupDetail&amp;groupID=3413">Expert Group</a>, mostly consisting of member states' public agencies, to come up with recommendations. Unfortunately, as of June 2019, the majority of the group intends to make broad and diffuse device categories like "Software Defined Radio" and "Internet of Things" a subject of radio lockdown.</p>
  28. <h2 id="threats">Why is Radio Lockdown dangerous?</h2>
  29. <p>First of all, the scope is immense. Radio devices are everywhere and increasingly many devices connect using wireless and mobile networks. The influence of this technology in our daily lives continously grows. Therefore, it is more important than ever to ensure that users are not restricted. But Article 3(3)(i) does not enforce only a certain security measurement, but drastically limits the control that customers have over the technology they own.</p>
  30. <p>For each of the following areass, we see a number of issues caused by Radio Lockdown, as we explain in the following.</p>
  31. <h3 id="freesoftware">Software freedom</h3>
  32. <p>To control technology, we have to be able to control the software running it. This only is possible with <a href="/about/basics/freesoftware.html">Free Software</a>. So if we want to have transparent and trustworthy devices, we need to make the software running on them Free Software. But any device affected by Article 3(3)(i) will only allow the installation of software which has been authorised by the device manufacturer. It is unlikely that a manufacturer will certify all the available, perfectly legal software for its device. This turns manufacturers into gatekeepers, and with their particular interests they may make it more difficult to use Free Software on radio devices.</p>
  33. <h3 id="compliance">Licence compliance</h3>
  34. <p>A large number of radio devices uses Free Software such as GNU/Linux, the GNU C Library or Samba which are licenced under the popular GNU GPL, LGPL or AGPL licences. The <a href="https://download.fsfe.org/policy/radiodirective/RED_Legal_Study_Jaeger-2019.pdf">Legal Study on the Radio Equipment Directive's Potential Ramifications for FOSS</a> by the renowed lawyer Dr. Till Jaeger found that Article 3(3)(i) is incompatible with the licence conditions of GPL-3.0, LGPL-3.0 and AGPL-3.0 and probably more Free Software licences like GPL-2.0 and LGPL-2.1:</p>
  35. <blockquote><p>It can be stated that widely used Free and Open Source Software programs as GNU/Linux, GNU C Library and Samba will not be able to be used in products which fall into the scope of Art. 3(3)(i) RED if the delegated acts of the European Commission do not provide for a limitation. Otherwise, the manufacturer would risk a copyright infringement since any violation of the license conditions of the GPL and LGPL results in an automatic termination of the rights granted.</p></blockquote>
  36. <p>This would put manufacturers using components under these licenses into a dangerous position. On the one hand, they have to set up a software lockdown on their devices, on the other hand they illegally breach the licence terms.</p>
  37. <h3 id="security">Security</h3>
  38. <p>Radio equipment like smartphones, routers, or smart home devices are highly sensitive parts of everyday life today. Unfortunately, many manufacturers sacrifice security for lower costs. For many devices there is better software which protects data and still offers equal or even better functionality. Users have to be able to protect themselves by installing safer and well-maintained software. But if certain manufacturers do not even care for security, it is unlikely that they will run a costly certification of third-party software.</p>
  39. <h3 id="competition">Competition</h3>
  40. <p>If customers don't like a certain product, they can use another from a different manufacturer. New competitors can access the market to convince customers with better features. But Article 3(3)(i) favours huge enterprises as it forces companies to install software barriers and do certification of additional software. For example, a small and medium-sized manufacturer of WiFI routers cannot certify all available Free Software operating systems and their different versions. Also, companies bundling their own software with third-party hardware will run into problems. On the other hand, large companies which don't want users to use any other software than their own will profit from this threshold.</p>
  41. <h3 id="environment">Environment</h3>
  42. <p>The life cycles of radio devices like mobile phones and routers continuously decrease. From a security perspective, there are only two options for a device which does not receive any vendor updates any more: install another firmware which still receives updates, or throw the whole device away. From an environmental perspective, the first solution is much better. But manufacturers do not have an incentive to certify alternative firmware for devices they want to get rid of.</p>
  43. <h3 id="society">Community Services</h3>
  44. <p>Charitable initiatives like <a href="https://freifunk.net">Freifunk</a>, <a href="https://funkfeuer.at">Funkfeuer</a>, <a href="http://ninux.org">Ninux</a>, or <a href="https://guifi.net">Guifi</a> depend on third-party hardware which they can use with their own software for their charity causes. They create innovative solutions for the public with limited resources. At the same time, they are dependent on devices which they can use with they own, individually adapted software.</p>
  45. <h2 id="getactive">What can I do?</h2>
  46. <p>Although organisations like the FSFE are continously fighting to limit the negative consequences of Radio Lockdown, we need your help! Here are a few proposals how you can contribute to our common efforts:</p>
  47. <ul>
  48. <li>Contact the European Commission, especially DG GROW, which is in charge of the delegated act, and your politcial representatives. Make them aware of your worries.</li>
  49. <li>Contact your national agencies or other actors which have a seat in the <a href="http://ec.europa.eu/transparency/regexpert/index.cfm?do=groupDetail.groupDetail&amp;groupID=3413">Expert Group</a> to show them that you care about this topic.</li>
  50. <li>Participate in <a href="https://ec.europa.eu/info/law/better-regulation/initiatives/ares-2018-6621038_en">public consultations</a>. You will learn about opportunities via <a href="/news">the FSFE's news channels</a>.</li>
  51. <li>If you represent a company or other industry actor, contact relevant business associations or the European Telecommunications Standards Institute (ETSI).</li>
  52. <li>If you represent a company or organisations concerned by Radio Lockdown, sign the <a href="/activities/radiodirective/statement.html">joint statement</a>.</li>
  53. </ul>
  54. </div><!--/e-content-->
  55. </body>
  56. <tags>
  57. <tag content="Radio Lockdown Directive">RadioDirective</tag>
  58. <tag content="Policy">Policy</tag>
  59. <tag content="Competition">Competition</tag>
  60. <tag content="European Parliament">EuropeanParliament</tag>
  61. <tag content="European Commission">EuropeanCommission</tag>
  62. </tags>
  63. <sidebar promo="our-work">
  64. <dynamic-content />
  65. <h2>Further Reading</h2>
  66. <ul>
  67. <li><a href="/activities/radiodirective/statement.html">Joint Statement against Radio Lockdown</a></li>
  68. </ul>
  69. <h3>External links</h3>
  70. <ul>
  71. <li><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0053">Full text and translations of RED 2014/53/EU</a></li>
  72. <li><a href="https://ec.europa.eu/info/law/better-regulation/initiatives/ares-2018-6621038">EU Commission's feedback portal and roadmap</a></li>
  73. <li><a href="https://download.fsfe.org/policy/radiodirective/RED_Legal_Study_Jaeger-2019.pdf">Legal Study on the Radio Equipment Directive’s Potential Ramifications for FOSS</a> by Dr. Till Jaeger</li>
  74. </ul>
  75. <h3>Latest News</h3>
  76. <ul>
  77. <fetch-news/>
  78. </ul>
  79. </sidebar>
  80. <timestamp>$Date$ $Author$</timestamp>
  81. </html>
  82. <!--
  83. Local Variables: ***
  84. mode: xml ***
  85. End: ***
  86. -->