Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Would a crypto file be acceptable?
Date: Wed, 28 Dec 2022 09:27:23 -0500
Message-ID: <CAEEMt2nHsebEcxJABQYzEq2wY+k2=rHTmYUk63xM0NvptQboRg@mail.gmail.com> (raw)
In-Reply-To: <CAPd6JnFxJccA3t7tLLZi-1p2stE1gjUT_cxoZQeOpgo1NKc=zA@mail.gmail.com>

Hi Mark,

On Tue, Dec 27, 2022 at 5:47 PM Mark Gaiser <markg85@gmail.com> wrote:

> The tricky part here is for anyone using this scheme to play this file.
> Right now i'm doing this with a command line like:
> ffplay crypto://encrypted_file -decryption_key $AES_KEY -decryption_iv
> $AES_IV
>
> For brevity's sake, consider the "metadata" file named above to be the
> _encrypted_ version of the ".crypto" file i'm proposing.
> [..]
>
There's many ways to do this key part. My intention for now was to keep it
> "simple" and have the key in the file itself.
>

There's multiple things going on here, and you're sort of putting them all
together to solve all problems at once:
- a mechanism for crypto-data exchange in your application or server/client
protocol
- a way for your application to pass the crypto-data to the underlying
library

I think once you split these out as separate entities, you'll see that you
don't necessarily need the same solution for it. The second one, in
particular, is already solved in FFmpeg, and this is called an AVOption.
(And the first question is really out of FFmpeg scope anyway.) Have you
considered simply using AVOption, and/or is there a reason AVOption isn't a
suitable solution for your use case?

Ronald
_______________________________________________
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".

  reply	other threads:[~2022-12-28 14:27 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
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 [this message]
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='CAEEMt2nHsebEcxJABQYzEq2wY+k2=rHTmYUk63xM0NvptQboRg@mail.gmail.com' \
    --to=rsbultje@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