Tweet
The reason is GStreamer loads the untrusted code at runtime. It would cause a potential security breach to the Chrome's security architecture.
Chromium runs RenderProcess (HTML, CSS, JavaScript) in a separate process with less access to platform/OS resources. If chromium uses GStreamer, then GStreamer should have run as a part of RenderProcess which finally tends to load some untrusted plugin code. GStreamer's plugin may need some system privileges to run, but it may fail because RenderProcess is already sandboxed.
What happens if security is breached because of the untreated GStreamer plugin? You blame Chromium right?
Chromium runs RenderProcess (HTML, CSS, JavaScript) in a separate process with less access to platform/OS resources. If chromium uses GStreamer, then GStreamer should have run as a part of RenderProcess which finally tends to load some untrusted plugin code. GStreamer's plugin may need some system privileges to run, but it may fail because RenderProcess is already sandboxed.
What happens if security is breached because of the untreated GStreamer plugin? You blame Chromium right?
Comment