From: Mark Gaiser <markg85@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Would a crypto file be acceptable? Date: Fri, 23 Dec 2022 17:31:41 +0100 Message-ID: <CAPd6JnF0fo=2rg-VxrpxC8rn96WMuS2p5E1cHDk72BN7dJSFWw@mail.gmail.com> (raw) In-Reply-To: <4e55583552e6075a98529e687aa734ae3a37d434.camel@haerdin.se> On Fri, Dec 23, 2022 at 12:05 PM Tomas Härdin <git@haerdin.se> wrote: > ons 2022-12-21 klockan 16:44 +0100 skrev Mark Gaiser: > > Hi, > > > > The ffmpeg crypto protocol handler [1] allows one to play encrypted > > media. > > > > The great thing here is that it allows playback of any media format > > that > > ffmpeg supports! > > Have a container format like mkv as an encrypted blob, no problem for > > the > > crypto plugin! > > > > I'm explicitly mentioning mkv (though there's many more) here because > > that > > isn't possible in HLS/MPD. While those streaming formats handle > > encryption > > too, they are very limited in terms of supported codecs and > > containers. > > > > Playback of encrypted data works like this: > > ffplay encrypted_file -decryption_key $AES_KEY -decryption_iv $AES_IV > > > > While this works just fine, it's limited in use because the > > cryptography > > details have to be passed on the command line. Applications that > > might well > > support much of ffmpeg functionality can't easily hook into the > > crypto > > functionality. Take KODI for example, it allows playback of many of > > the > > formats ffmpeg supports but anything with crypto just isn't possible. > > In > > fact, anything that requires custom command line arguments isn't > > possible. > > This sounds like business logic. Fix KODI instead. Much of this can > also be handled by any competent OS at the filesystem layer. > Then M3U as a format is business logic too. HLS and MPD are business logic too. At least, based on your comment, they would fall into that same category. The difference between those formats and my suggestion? M3U -> playback of very specific formats "crypto" -> playback of anything ffmpeg supports M3U has a file format. crypto has none. Say a hypothetical streaming service (no, i don't have ambitions to start one) would want to give access to higher quality and different codecs then is possible with HLS/MPD. A service like that currently has to invent their own custom format, probably as a fork of ffmpeg, to accomplish this. With a file format for crypto this functionality would just exist. I'm suggesting that giving crypto this file format would be a win with not even that much effort on the ffmpeg code side. > /Tomas > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-12-23 16:32 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-21 15:44 Mark Gaiser 2022-12-21 16:00 ` Mark Gaiser 2022-12-22 19:14 ` Gregor Riepl 2022-12-23 1:26 ` Mark Gaiser 2022-12-23 17:45 ` Gregor Riepl 2022-12-22 10:40 ` Nicolas George 2022-12-22 15:53 ` Mark Gaiser 2022-12-22 17:50 ` Hendrik Leppkes 2022-12-23 11:04 ` Tomas Härdin 2022-12-23 16:31 ` Mark Gaiser [this message] 2022-12-23 16:33 ` Nicolas George 2022-12-23 17:00 ` Mark Gaiser 2022-12-23 17:38 ` Nicolas George 2022-12-26 10:58 ` Tomas Härdin 2022-12-26 11:00 ` Nicolas George 2022-12-26 11:18 ` Tomas Härdin 2022-12-26 11:24 ` Nicolas George 2022-12-27 18:24 ` Mark Gaiser 2022-12-27 21:40 ` Michael Niedermayer 2022-12-27 22:46 ` Mark Gaiser 2022-12-28 14:27 ` Ronald S. Bultje 2022-12-28 16:13 ` Mark Gaiser 2022-12-28 16:22 ` Nicolas George 2022-12-28 16:27 ` Mark Gaiser 2022-12-28 16:30 ` Nicolas George 2022-12-28 16:58 ` Mark Gaiser 2022-12-29 14:04 ` Ronald S. Bultje 2022-12-28 21:02 ` Michael Niedermayer 2022-12-29 14:51 ` Mark Gaiser 2022-12-29 22:34 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAPd6JnF0fo=2rg-VxrpxC8rn96WMuS2p5E1cHDk72BN7dJSFWw@mail.gmail.com' \ --to=markg85@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git