Closed
Bug 876574
Opened 11 years ago
Closed 11 years ago
Construct fixed pipeline in gstreamer backend
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: eflores, Assigned: eflores)
References
Details
Attachments
(1 file)
12.76 KB,
patch
|
Details | Diff | Splinter Review |
The gstreamer backend currently uses playbin to automatically construct a pipeline. For security, we should construct known-good pipelines manually.
Comment 1•11 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.
Comment 2•11 years ago
|
||
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.
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #776127 -
Flags: review?(alessandro.d)
Assignee | ||
Updated•11 years ago
|
Attachment #776127 -
Flags: review?(alessandro.d)
Assignee | ||
Comment 4•11 years ago
|
||
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
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•