After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 720780 - DTCP/IP support needed when using proposed dlnasrc from issue #709455
DTCP/IP support needed when using proposed dlnasrc from issue #709455
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.x
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-12-19 22:32 UTC by Steve Maynard
Modified: 2018-05-06 08:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gstdtcpip and lib_dtcpip (34.60 KB, patch)
2013-12-19 22:32 UTC, Steve Maynard
none Details | Review

Description Steve Maynard 2013-12-19 22:32:01 UTC
Created attachment 264580 [details] [review]
gstdtcpip and lib_dtcpip

A DTCP (Digital Transmission Content Protection) element is needed to interface to a private DTCP/IP decrypting library to handle encrypted (link protected) content from a DTCP/IP enabled DLNA (Digital Living Network Allicance) server.

This enhancement issue holds the patches for a gstdtcpip element that is part of the dlnasrc bin.

The dtcpip element will not actually perform decryption.  DTCP is governed by a specification that is managed by DTLA (www.dtcp.com) and only member organizations can access the spec and produce implementations.  This solution abstracts the actual DTCP stack via an API that is accessed by making function calls to runtime-loaded DSO.  The intention is to provide a GStreamer element that extends decryption capability once a proprietary DTCP library implementation is referenced by the appropriate environment variables.

The dtcpip element does not autoplug, but rather gets plugged in by the dlnasrc.  There was controversy over this as described in issue #709455.
Comment 1 Sebastian Dröge (slomo) 2014-01-03 09:51:55 UTC
Why is the element not autoplugged now? The conclusion in bug #709455 was to do that AFAIU.
Comment 2 Sebastian Dröge (slomo) 2014-01-15 14:34:39 UTC
Ping? :) Also see bug #705991 about a similar problem, CENC. We should handle them ideally the same way.
Comment 3 Brendan Long 2014-01-15 16:01:20 UTC
Our team has become significantly smaller recently, so I might end up working on this. Right now I have a very large backlog though. I'm hoping to have a plan for what I'll be working on later this week.
Comment 4 Edward Hervey 2018-05-06 08:26:42 UTC
Thanks for the patch, but this is not something we can work on (nor test). And nothing prevents you from having the element available in a 3rd party repository.