level 13
level 13
709922234
楼主
这里是一个 Demo https://github.com/cpearce/mse-eme
2018年09月26日 04点09分
2
我开始以为 key 是 DRM 管理器如 widewine 内部进行获取的，但是看这个 demo 并不是这样的啊，好像是 cdm 模块发出的 message，然后应用去拿 key 然后给 cdm 啊
2018年09月26日 04点09分
Note that there may be multiple messages between the CDM and the license server, and all communication in this process is opaque to the browser and application。
2018年09月26日 07点09分
level 10
![[不高兴]](/static/emoticons/u4e0du9ad8u5174.png)
level 13
709922234
楼主
From the EME spec:
The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation). License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies.
This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Implementation of Digital Rights Management is not required for compliance with this specification: only the Clear Key system is required to be implemented as a common baseline.
The common API supports a simple set of content encryption capabilities, leaving application functions such as authentication and authorization to page authors. This is achieved by requiring content protection system-specific messaging to be mediated by the page rather than assuming out-of-band communication between the encryption system and a license or other server.
2018年09月26日 05点09分
4
The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation). License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies.
This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Implementation of Digital Rights Management is not required for compliance with this specification: only the Clear Key system is required to be implemented as a common baseline.
The common API supports a simple set of content encryption capabilities, leaving application functions such as authentication and authorization to page authors. This is achieved by requiring content protection system-specific messaging to be mediated by the page rather than assuming out-of-band communication between the encryption system and a license or other server.
level 13
level 10
常见的许可证有 GPL BSD MIT 等等，眼睛回去再看一眼“常见的”这个形容词。开头一个是传染衍生品的，后两个几乎没有传染性。除此之外， AGPL 能传染服务器，网站上的软件被传染。看好了常见的许可证，再看鲜为人知的许可证： Sybase Open Watcom 许可证。它的传染性极强，连 AGPL 也甘拜下风。 Sybase Open Watcom 传染到断网的版本，就是用户不搭服务器也被传染。 Richard M. Stallman 评论说它并不自由，但开源社区承认它是开源软件。 Richard M. Stallman 身正不怕影子斜，开源社区却上梁不正下梁歪。综上所述，自由软件和开源软件的区别很多，甚至需要考试，只可惜没有一个学校考这个。如果我是校长，我就新增这个考试，答错直接扣 41 分；如果满分 100 ，答错直接不及格。
2020年01月17日 10点01分
6
