From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 757C743FA7
	for <ffmpegdev@gitmailbox.com>; Fri, 23 Dec 2022 11:05:04 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 488B068BA74;
	Fri, 23 Dec 2022 13:05:03 +0200 (EET)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9CBB468BA72
 for <ffmpeg-devel@ffmpeg.org>; Fri, 23 Dec 2022 13:05:00 +0200 (EET)
Received: from [192.168.1.75] (217-208-223-222-no2430.tbcn.telia.com
 [217.208.223.222])
 by mail.frobbit.se (Postfix) with ESMTPSA id 2B9BA21C23
 for <ffmpeg-devel@ffmpeg.org>; Fri, 23 Dec 2022 12:05:00 +0100 (CET)
Message-ID: <4e55583552e6075a98529e687aa734ae3a37d434.camel@haerdin.se>
From: Tomas =?ISO-8859-1?Q?H=E4rdin?= <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Date: Fri, 23 Dec 2022 12:04:59 +0100
In-Reply-To: <CAPd6JnHEYqvDDy3b31ow4DCS8DiQ4U9ei7==3DL-9kEXum2sWw@mail.gmail.com>
References: <CAPd6JnHEYqvDDy3b31ow4DCS8DiQ4U9ei7==3DL-9kEXum2sWw@mail.gmail.com>
User-Agent: Evolution 3.38.3-1+deb11u1 
MIME-Version: 1.0
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 <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/4e55583552e6075a98529e687aa734ae3a37d434.camel@haerdin.se/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

ons 2022-12-21 klockan 16:44 +0100 skrev Mark Gaiser:
> Hi,
> 
> The ffmpeg crypto protocol handler [1] allows one to play encrypted
> media.
> 
> The great thing here is that it allows playback of any media format
> that
> ffmpeg supports!
> Have a container format like mkv as an encrypted blob, no problem for
> the
> crypto plugin!
> 
> I'm explicitly mentioning mkv (though there's many more) here because
> that
> isn't possible in HLS/MPD. While those streaming formats handle
> encryption
> too, they are very limited in terms of supported codecs and
> containers.
> 
> Playback of encrypted data works like this:
> ffplay encrypted_file -decryption_key $AES_KEY -decryption_iv $AES_IV
> 
> 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.

This sounds like business logic. Fix KODI instead. Much of this can
also be handled by any competent OS at the filesystem layer.

/Tomas

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