If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Construct fixed pipeline in gstreamer backend

RESOLVED WONTFIX

Status

()

Core
Audio/Video
RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: eflores, Assigned: eflores)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

The gstreamer backend currently uses playbin to automatically construct a pipeline.

For security, we should construct known-good pipelines manually.

Comment 1

4 years ago
If we really want to do this, there's a way to tap in in the autoplug mechanism and whitelist/blacklist things. playbin does a bunch of useful things that would be pointless to duplicate.
If we can reliably blacklist *everything* except the specific nodes that we need, that should be sufficient. We do this in the Windows Media Foundation backend.
Blocks: 886181
Created attachment 776127 [details] [diff] [review]
Whitelist elements
Attachment #776127 - Flags: review?(alessandro.d)
Attachment #776127 - Flags: review?(alessandro.d)
After talking on IRC, Alessandro and I concluded that there's no real way of doing this, as there is no way to uniquely identify plugins. Resolving WONTFIX.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.