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 7381244ED5 for ; Wed, 28 Dec 2022 16:14:19 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5DE6668B371; Wed, 28 Dec 2022 18:14:16 +0200 (EET) Received: from mail-ed1-f47.google.com (mail-ed1-f47.google.com [209.85.208.47]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id D0B1868080D for ; Wed, 28 Dec 2022 18:14:09 +0200 (EET) Received: by mail-ed1-f47.google.com with SMTP id z11so7524807ede.1 for ; Wed, 28 Dec 2022 08:14:09 -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=a5LCtmwUmF84zAt6j3QnBMSyPm0Lc9N2Znmxj99OhEk=; b=n1VUB4A8RqdzML51gvPcRX+yY3MKvUBWFNeIquyyPQ+mBWj7A4sscRdgulX9uXjxSN kZx7ZR+LKZXVB3Xu4xmd4jBhyyZ7cwPvSA38qrNfYWAC2EkCj2o2uxZBKDnnsyOQcJg0 up5WrJprr7acfAgQVuwLWHw4/PtrQy/jaEEEkk+u4Sn5JhKwiT7hyjEgLwlloUplGOnd aMahUYTCtCNXuW+Ty68NkJco9zVRKmfYGxDQqRvPz6bgXR36KQROr7gkK7SRoSsHBPzf +a+G8IHH03YW1f69YktUY8jhKYyYZQW+70TSjwQa+gIGFAQMZOGX7Jwt+kfsT4ORl5LD +uVg== 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=a5LCtmwUmF84zAt6j3QnBMSyPm0Lc9N2Znmxj99OhEk=; b=z2XNZGzZm8k8GKv/pwoJammeIBncVZ5piScfxrToxFGjIAUrjJbq56/a2R3gNzSPy+ jizaFlwHDVoBXUycOFUNDBvPb8g/JTEWyfl2qI49qPKcsALxRoRCWy0sVHBGl9AziG0z JStQN0z23DHVTWfQwUxQMbAmVqSWI5A7avPWeodD6QDJAQO6qsZLxF/TLsrHAVWDNYgO z7unDAOxumMeFjSYAKLdk1oKMeKW/vZcXfSsHVNtKaPLOggK8AoRwishpztV/mD2TmOA DxkbDog7zwqL8wNRkWG0Qqil652nHY1w8sgccT4PZycHHi0Nq3cP6lWWJYzz93teYX8x +4VQ== X-Gm-Message-State: AFqh2kpPkvJFTIs8XJ/ofFKKxyoFwswTt62CCd6nkrs1cdRIegQH3wVU xTUIDGTQY2SqZ/lxRhfpGYxin4iTRzMBH1jAevzn6bNvqcA= X-Google-Smtp-Source: AMrXdXskhKws74y+A+GQKWK2Lcg+WyYQhsmZLlgS6Ve872uexTRWvvcl1FShDWYDUaPBePgAeEyAwJT+ijsoHu8KZKg= X-Received: by 2002:a05:6402:22a6:b0:46c:80f3:c0c0 with SMTP id cx6-20020a05640222a600b0046c80f3c0c0mr1958263edb.424.1672244048685; Wed, 28 Dec 2022 08:14:08 -0800 (PST) MIME-Version: 1.0 References: <20221227214033.GS3806951@pb2> In-Reply-To: From: Mark Gaiser Date: Wed, 28 Dec 2022 17:13:46 +0100 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: 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. Today this works: ffplay crypto://encrypted_file -decryption_key $AES_KEY -decryption_iv $AES_IV I'm proposing: ffplay encrypted_file.crypto The ".crypto" file hides the details that you'd otherwise have to pass manually. I am proposing a format for that file and was hoping for constructive feedback to make sure I develop a format that is OK by the ffmpeg team and could potentially be accepted when I send it as a PR. That is the discussion I wanted to have here. Not needless back and forth in details that "matter to my endgoal" but don't matter for the feature i'm proposing. With regards to your AVOption option remark. What you don't say, but imply by it, is implementing ".crypto" support on a per-application basis completely outside of ffmpeg. That's a total 180 turn of what I meant to ask and not the intention at all! _______________________________________________ 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".