From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Would a crypto file be acceptable?
Date: Thu, 22 Dec 2022 18:50:16 +0100
Message-ID: <CA+anqdwfeNfiEde+6QcWkXx5CmzCvPPdFZGjPMm3isixcZRNdg@mail.gmail.com> (raw)
In-Reply-To: <CAPd6JnEpt6iBmia+RW0jqnOhfbjyBZnLcrBm7G7KwWYhzgNKdw@mail.gmail.com>
On Thu, Dec 22, 2022 at 4:53 PM Mark Gaiser <markg85@gmail.com> wrote:
>
> On Thu, Dec 22, 2022 at 11:40 AM Nicolas George <george@nsup.org> wrote:
>
> > Mark Gaiser (12022-12-21):
> > > 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.
> > > [2]
> > >
> > > My idea is to make a new file format that would be implemented and
> > specced
> > > within [1]. My proposed format would be:
> > >
> > > ---
> > > CRYPTO-VERSION:1
> > > CRYPTO-KEY:URI:.....
> > > CRYPTO-IV:URI:.....
> > > encrypted_file
> > > ---
> >
> > The concat demuxer can already contain options, and despite is name it
> > can be used with a single file.
> >
>
> Could you elaborate on how to use that:?
>
> The end result needs to be:
> ffplay <file>
>
> that needs to translate to:
> ffplay crypto://encrypted_file -decryption_key $AES_KEY -decryption_iv
> $AES_IV
>
> I briefly looked at the concat demuxer but couldn't see how to get this
> desired result.
> If you know how, please let me know!
>
Create a file like this:
https://pastebin.com/hFSeXsZt
The first line is so ffmpeg can probe the format, then just have a
"file" line followed by any number of "option" lines.
Note that options are only allowed if safe-mode is disengaged, so the
app in question would have to pass "-safe 0" to the execution in some
manner. But this is something you would have to ask the app to do, as
this protection exists for a reason.
- Hendrik
_______________________________________________
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-22 17:50 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 [this message]
2022-12-23 11:04 ` Tomas Härdin
2022-12-23 16:31 ` Mark Gaiser
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=CA+anqdwfeNfiEde+6QcWkXx5CmzCvPPdFZGjPMm3isixcZRNdg@mail.gmail.com \
--to=h.leppkes@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