9:4
| Encrypted Media Extensions | |
| Native name | Encrypted Media Extensions |
|---|---|
| Status | W3C Recommendation |
| Year started | 2013 |
| First published | May 10, 2013[1] |
| Latest version | 2017-09-18 September 18, 2017[2] |
| Preview version | Editor's Draft March 20, 2021[3] |
| Organization | [2][3] |
| Committee | |
| Editors | |
| Base standards |
|
| Domain | Digital rights management |
| Abbreviation | EME, encrypted-media |
| Website |
|
Encrypted Media Extensions (EME) is a W3C specification for providing a communication channel between web browsers and the Content Decryption Module (CDM) software which implements digital rights management (DRM).[2] This allows the use of HTML5 video to play back DRM-wrapped content such as streaming video services without the use of heavy third-party media plugins like Adobe Flash or Microsoft Silverlight. The use of a third-party key management system may be required, depending on whether the publisher chooses to scramble the keys.
EME is based on the HTML5 Media Source Extensions (MSE) specification,[4] which enables adaptive bitrate streaming in HTML5 using e.g. MPEG-DASH with MPEG-CENC protected content.[5][6]
EME has been highly controversial because it places a necessarily proprietary, closed decryption component which requires per-browser licensing fees into what might otherwise be an entirely open and free software ecosystem.[7][8] On July 6, 2017, W3C publicly announced its intention to publish an EME web standard,[9] and did so on September 18.[2] On the same day, the Electronic Frontier Foundation, who joined in 2014 to participate in the decision making,[10] published an open letter resigning from W3C.[11]
In April 2013, on the Samsung Chromebook, Netflix became the first company to offer HTML5 video using EME.[12]
As of 2016[update], the Encrypted Media Extensions interface has been implemented in the Google Chrome,[13]Internet Explorer,[14]Safari,[15]Firefox,[16] and Microsoft Edge[17] browsers.
While backers and the developers of the Firefox web browser were hesitant in implementing the protocol for ethical reasons due to its dependency on proprietary code,[18] Firefox introduced EME support on Windows platforms in May 2015, originally using Adobe's Primetime DRM library, later replaced with the Widevine library (CDM). Firefox's implementation of EME uses an open-source sandbox to load the proprietary DRM modules, which are treated as plug-ins that are loaded when EME-encrypted content is requested. The sandbox was also designed to frustrate the ability for services and the DRM to uniquely track and identify devices.[16][19] Additionally, it is always possible to disable DRM in Firefox, which then not only disables EME, but also uninstalls the Widevine DRM libraries.[20]
Netflix supports HTML5 video using EME with a supported web browser: Chrome, Firefox,[21] Microsoft Edge, Internet Explorer (on Windows 8.1 or newer[22]), or Safari (on OS X Yosemite or newer[23]). YouTube supports the HTML5 MSE.[24] Available players supporting MPEG-DASH using the HTML5 MSE and EME are NexPlayer,[25] THEOplayer[26] by OpenTelly, the bitdash MPEG-DASH player,[27][28] dash.js[29] by DASH-IF or rx-player.[30]
Note that certainly in Firefox and Chrome, EME does not work unless the media is supplied via Media Source Extensions.
Version 4.3 and subsequent versions of Android support EME.[31]
EME has faced strong criticism from both inside[33][34] and outside W3C.[35][36] The major issues for criticism are implementation issues for open-source browsers, entry barriers for new browsers, lack of interoperability,[37] concerns about security, privacy and accessibility, and possibility of legal trouble in the United States due to Chapter 12[38] of the DMCA.[39][40][41][42]
There are potential security issues introduced when running any form of DRM software. Since the software is proprietary — and therefore not open source — vulnerabilities are obscured from code audit.
Exposing DRM modules that cannot be properly audited to web content, which is untrustworthy, may result in such software being abused and/or attacked by any website the user visits with the DRM software enabled. While Firefox does attempt to prevent malicious code from escaping its sandbox, there is no guarantee that the sandbox will work.
In July 2020, Reddit started running a javascript program that launches a fingerprinting attack (which makes it possible to persistently track individuals around the web) against the user's web browser. Part of the script attempts to load every possible DRM module that browsers can support, and logs what ends up loading as part of the data collected. Users noticed this when Firefox began alerting them that Reddit "required" them to load DRM software to play media, although none of the media on the page actually needed it.[43]
As of 2020, the ways in which EME interferes with open source have become concrete. None of the widely used CDMs is being licensed to independent open-source browser providers without paying a per-browser licensing fee.[7]
In mobile markets [...] Android has supported MSE since version 4.1, and EME since version 4.3.
Note that IE10 and IE11 on Windows 7 do not have the MSE/EME API available which is required to playback DRM protected video content in HTML5. As a consequence, it is technically not possible for any HTML5-based video player to playback DRM protected content on these browsers in Windows 7.
By: Wikipedia.org
Edited: 2021-06-18 14:12:21
Source: Wikipedia.org
