Source files of,,,,, and Contribute:
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.

news-20140506-01.en.xhtml 2.9KB

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <html newsdate="2014-05-06">
  3. <head>
  4. <title>Open Letter to European Commission: Stop DRM in HTML5</title>
  5. </head>
  6. <body class="press release">
  7. <h1>Open Letter to European Commission: Stop DRM in HTML5</h1>
  8. <p newsteaser="yes">On today's <a href="">"Day
  9. against DRM"</a>, the Free Software Foundation Europe (FSFE) has sent <a
  10. href="/activities/drm/open-letter-ec-drm-html.html">an open letter to the
  11. European Commission, asking the EC to prevent Digital
  12. Restrictions Management technology from being closely integrated
  13. with the HTML5 standard</a>.</p>
  14. <p>FSFE is concerned about efforts currently in progress at the
  15. World Wide Web Consortium (W3C), to encourage the integration of Digital
  16. Restriction Management (DRM) technology into web browsers. The
  17. W3C oversees many of the key standards on which the World Wide Web
  18. is based.</p>
  19. <p>
  20. A W3C working group is currently standardising an "Encrypted Media
  21. Extension" (EME), which will allow companies to easily plug in
  22. non-free "Content Decryption Modules" (CDM) with DRM
  23. functionality, taking away users' control over their own
  24. computers. Most DRM technologies impose restrictions on users that
  25. go far beyond what copyright and consumers' rights allow.
  26. </p>
  27. <blockquote><p>"Integrating DRM facilities into HTML5 is the
  28. antithesis of everything that has made the Internet and the
  29. World Wide Web successful," says FSFE's President Karsten
  30. Gerloff. "It is directly contrary to the interests of the vast
  31. majority of Internet users everywhere."</p></blockquote>
  32. <p>Auditing the DRM modules will be both difficult and
  33. illegal. Their source code will be a closely held secret of the company
  34. which distributes the module. Performing an audit and reporting security
  35. flaws would also be illegal in the many countries which have
  36. adopted so-called "anti-circumvention" laws. Reporting a security
  37. problem in the DRM module would expose the reporter to the risk of
  38. lawsuits from the makers of that module. </p>
  39. <p>FSFE asks the European Commission to:</p>
  40. <ul>
  41. <li>Engage with the W3C and ensure that the organisation takes
  42. these concerns on board as it decides on the adoption of the Encrypted
  43. Media Extension (EME).</li>
  44. <li>Pledge not to make use of the Encrypted Media Extension in
  45. its own infrastructure, even if EME were to be standardised by
  46. W3C.</li>
  47. <li>Protect people and companies from prosecution who
  48. reverse-engineer DRM technology and report vulnerabilities.</li>
  49. </ul>
  50. </body>
  51. <sidebar news="free software, security, DRM, Open Standards">
  52. </sidebar>
  53. <tags>
  54. <tag>front-page</tag>
  55. <tag>DRM</tag>
  56. <tag>W3C</tag>
  57. <tag>OpenLetter</tag>
  58. <tag>Policy</tag>
  59. </tags>
  60. </html>