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 48B4A44EF8 for ; Thu, 29 Dec 2022 14:04:30 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 16E0268B720; Thu, 29 Dec 2022 16:04:27 +0200 (EET) Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id D6EE668B305 for ; Thu, 29 Dec 2022 16:04:20 +0200 (EET) Received: by mail-ed1-f54.google.com with SMTP id d14so26776136edj.11 for ; Thu, 29 Dec 2022 06:04:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=baNQOUOjo3kWlhvyLi3TMhsPquuipzCUN681RObiGEw=; b=YmZaHTVVjnMUWUfZw3segnLovzsGMI19nTx+ooL+o1EDCikHAx8mlZLm2LEW2elm64 F4tsCT5IuucgMKiun+0piJGPxownqC0Lob4Jfp+CRNDyRuLzX0oUTcNrKECviNm5vZIu Fgd2H8JtT+xtRASOj2LQklD02pNC3W8k5SiZJb2Vw+SRtap5yK2wssapzAzrWstShy+F mlq6FHWCZBYB977Y168C725GJdGkbntmsdhL4lzrgKQN6fjd12zD8Ibz41Lbk2PU20SZ yfbMY/E4hQZOJ2avIjkHIcFmR18ir+LnAUq90jkEt6GmEzbFg1Qsg2+Mc4KyEhTGRhRX bM0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=baNQOUOjo3kWlhvyLi3TMhsPquuipzCUN681RObiGEw=; b=GdueBQGEdnexppkCR9Dp5a0cg/0sDBYk09zS57VU7+U+WyEdkm0Ihy+OW9wnkpBhFY yIB/PIm2bAsShVjXMy9jduwAuxU7Sv0aPxa6rOBOkgSOcgLVsY2eduQLtlPq4AWTiQZy dxLsUBcUTBjMd//ju3Ed60unCDtApfQs2KMLSbl/cbuKg77BVTmJ8Qyvn3+MY9AI0MtT /QYLtRqINVNb0vtEi4Xh7IHSL0QISm8UH6yfHBnN9BufqvHid4ngkui17hmo5q5E+1Bv CZSB99UXhBFHT8mY5zg0+Gmeg3crBC/H15t1YlYImG4qzgWl+BzLBUdAETC4A0p2IX8q +T9Q== X-Gm-Message-State: AFqh2kousSaMjMlLxWzWvlUt6pi2YDpMKmU46BSLIEAL/cX0jFF8D7Vv tfLxQs9rlDN0anxezLh7WGMDp5RpzanWFb7OVmJq/o/6 X-Google-Smtp-Source: AMrXdXvXss103nYSqYqbekndp1lZjM5SgdGIOwu5aYAkwy8btKusuDkOQMWe6mNudm7VuKhNgsgbrO34QDsm+Lea62k= X-Received: by 2002:a05:6402:1550:b0:482:20e:5fbf with SMTP id p16-20020a056402155000b00482020e5fbfmr1500706edx.57.1672322659764; Thu, 29 Dec 2022 06:04:19 -0800 (PST) MIME-Version: 1.0 References: <20221227214033.GS3806951@pb2> In-Reply-To: From: "Ronald S. Bultje" Date: Thu, 29 Dec 2022 09:04:08 -0500 Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Hi, On Wed, Dec 28, 2022 at 11:14 AM Mark Gaiser wrote: > On Wed, Dec 28, 2022 at 3:27 PM Ronald S. Bultje > wrote: > > > Hi Mark, > > > > On Tue, Dec 27, 2022 at 5:47 PM Mark Gaiser 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? > > > > Hi Roland, > > There's definitely multiple things going on but it's not what you > summarize. > > 1. DEV (me) goes to the mailing list to propose a new feature. Dev tries to > be concise and to the point to not litter the request with irrelevant side > details. > 2. MU (mailing list user) is skeptical and needs more context - which is > great! > 3. DEV gives more context > 4. MU now discusses irrelevant side-details that DEV tried to prevent in > the initial post - this is where things go wrong > 5. Topic is now derailed with side suggestions that have nothing todo with > the initial proposal. Feature potentially never gets built. > > Point 5 is where we're roughly at right now. I will make this feature > because I need to have it for my own project. > > I'm fine discussing the proposed format further. > I know _exactly_ what i want to do. > But why? This is not a format. It's not a container, or a playlist. It's an artificial key/value exchange protocol created just for you. That's even the specific purpose of this format: it has no other purpose than to circumvent AVOption because it's ... complicated? I really don't understand why this is preferable over AVOption. Yet, you refuse to discuss this. And aside: the "DEV" and "MU" people in your story are much more than a fabulous white hat hacker vs. internet troll which you make it out to be (in what order?). Don't forget "MU" carries the long-term maintenance burden. This is not derailing; this is called design review. 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".