Chromium Edge, which is a combination of Edge and Chromium, has the potential to tackle the aforementioned issues with browser DRM. In conclusion, there is no way that it could be a solution.

Through evaluating the preview version of Edge, I discovered that the DRM functionality offered by Chromium Edge varies depending on the operating system in the following ways:

Chrome’s Edge browser for Microsoft Windows 10

Both PlayReady and Widevine DRM are supported by the version of Chromium Edge that is installed in Windows 10. This is the first major browser that has two digital rights management systems (DRMs)an anti-piracy toolincorporated in it.

When PlayReady is used for playing DRM content, it offers the same level of support for hardware-level DRM and the ability to prohibit screen recording as the present version of Edge. Because Widevine DRM uses software level security rather than hardware level security, the video can be recorded from the screen using a screen recorder.

When providing content protected by digital rights management (DRM), one thing to bear in mind is that the Windows 10 version of Chromium Edge may require you to adjust the DRM detection mechanism in your browser.

Web sites that play multi-DRM content are required to detect the types of DRM and Encrypted Media Extension (EME), and then apply the DRM settings that are appropriate for the environment of the browser. It is possible that Chromium Edge will be identified as a Chrome browser if the logic is developed to check only the user agent information of the browser or the presence of Widevine. In such scenario, the DASH material will be played using Widevine DRM rather than PlayReady, and you will miss out on the benefits of PlayReady, such as the avoidance of screen recording and hardware DRM.

Even though it is technically possible for a studio or content producer to use AES protection for their own content on their own, it is possible that they will not be able to plug the hardware-based leakages or stop the insecure transmission of AES keys between devices or between the server and the client device. This is because hardware-based leakages are caused when there is a mismatch in the encryption algorithms used by the server and the client device. This is because the only people who can seal leaks caused by hardware are the people who make the hardware. This is owing to the fact that leaks created by hardware can only be patched by an external entity that has access to the hardware in issue. The reason for this is as follows: When it comes to securing video content with an AES layer, a multi-DRM solution is utilised, and the selection of this option is what bridges the gap that has been established in this regard.

By admin