[FFmpeg-trac] #1793(avformat:open): Widevine support

[FFmpeg]

#1793: Widevine support
--------------------------------------+------------------------------------
             Reporter:  benito2313    |                    Owner:
                 Type:  enhancement   |                   Status:  open
             Priority:  wish          |                Component:  avformat
              Version:  git-master    |               Resolution:
             Keywords:  Widevine drm  |               Blocked By:
             Blocking:                |  Reproduced by developer:  0
Analyzed by developer:  0             |
--------------------------------------+------------------------------------

Comment (by saste):

 Replying to [comment:29 Kii-lon]:
 [...]
 > However, just a few minutes ago, I may...of found the Samsung FFmpeg
 source on an random git type site and I have no idea how to use such file
 or if it works but I found that the FFmpeg has the "widevine.c" file in an
 libav folder or somesort.
 >
 > Anyways I hope you guys don't mind me posting this but here's the link
 to
 > file in a zip format that I uploaded on both "Uppit" and "Mega".
 >
 > Uppit: [http://up.ht/TE02hv Uppit - Samsung FFmpeg?]
 > MEGA: [https://mega.co.nz/#!rA8wlCJL!gNzydQvEsWxPDxp-
 Yaifl_AP53ZNjuFGiL0XDwREZtE/ MEGA - Samsung FFmpeg?]
 >
 > If any of you guys can be kind, please give the file a look and see if
 it's indeed the so-called Samsung Patch, I hope i'm not wrong haha.
 [...]

 The second link (first one required a subscription) contained a hacked
 version of FFmpeg SVN rev19089 containing a wrapper to some proprietary
 library, and as is is an ugly hack which cannot be upstreamed.

 Note that widevine.c is implemented as a protocol, so it should be
 considered a protocol which allows to encrypt content (probably through
 DRM or similiar). AFAIK no effort was done by anyone of the FFmpeg team to
 reverse engineer the protocol format. Today I heard about partially
 encrypted files which can be played for the first few seconds (having such
 sample may help).

--
Ticket URL: <https://trac.ffmpeg.org/ticket/1793#comment:33>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker