From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 9509C4464A for ; Thu, 22 Dec 2022 10:40:29 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 147D968B8F2; Thu, 22 Dec 2022 12:40:25 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 2F547680446 for ; Thu, 22 Dec 2022 12:40:17 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 2BMAeG7m028165 for ; Thu, 22 Dec 2022 11:40:16 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id AB9F5EB5BC; Thu, 22 Dec 2022 11:40:16 +0100 (CET) Date: Thu, 22 Dec 2022 11:40:16 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Thu, 22 Dec 2022 11:40:16 +0100 (CET) Subject: Re: [FFmpeg-devel] Would a crypto file be acceptable? X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============3430069007801298846==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============3430069007801298846== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="lPEFwfLmFOlGGuR4" Content-Disposition: inline --lPEFwfLmFOlGGuR4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 we= ll > 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] >=20 > My idea is to make a new file format that would be implemented and specced > within [1]. My proposed format would be: >=20 > --- > 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. Regards, --=20 Nicolas George --lPEFwfLmFOlGGuR4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmOkNA4ACgkQcZVLI8pN xgxfAg/+N0smgA02fGG34wFjA07ISk+LLPqS5p/sfR6Hg3Ayyh1fdb2a3q3PWuVH U8oeE+LNlxYqjpcZT+27VgzO000O8UE9f6SAoYCzZlN/d+NCGc813+MDpg6caL8X cdAOfScrEP/qn0KQPmhY8xSDKwnuq4qmg8FoD5W7l6VH+OEJVr+ADEFRnq3PF4/m uZZFY0YuOt0SW0/hdYXSuEUlz1etzSSR0necBF4v8z4riijZoenDGRyq59N5utHB rQxXGXT+DtC5ZyNoL4cESPm6b40QEIEjF2SrHUXGtWbB8o1+wQ31apAdBAqi4O35 am2KAJKWSIStZS83jS06lt5GyZRATcXUWyxCQhXgd4L+pWYysQqXBZKI41vU4+Xm tKChYDGA/7jsnUaAz72vqGJPgBK8S/2d2wSdG2qzO5a1zARfeZ7glinX4iwfW/di w1FRzVQqUTO4lomrxZy+JKqyZHvN2boEV18mWvc4FuZoVKexKHK0qOb8s+mqRRPm A/FAJIi55pjxrxI7QzZztF3w5k1ILu3OjSTu6cN4A+qMMaPMelJhQQq/OcTl4LPz xCcgNHSvs8oxJw/HC8UG5VReMhE8r/2as2+ynA1pZpJte847/q1IlpOV9G0X0Igx HBweboYECnQo/QirbaRPFfnPWs4cCxRmcC5VvydJeFxDlIcatyI= =Q2Yo -----END PGP SIGNATURE----- --lPEFwfLmFOlGGuR4-- --===============3430069007801298846== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============3430069007801298846==--