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 15D7745D6F for ; Fri, 7 Jul 2023 08:06:01 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E9F6668C7B4; Fri, 7 Jul 2023 11:05:58 +0300 (EEST) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9437F68C755 for ; Fri, 7 Jul 2023 11:05:52 +0300 (EEST) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id B9F162404EC for ; Fri, 7 Jul 2023 10:05:51 +0200 (CEST) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id kO1SRua33hw0 for ; Fri, 7 Jul 2023 10:05:51 +0200 (CEST) Received: from lain.khirnov.net (lain.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 0FC7B2404EA for ; Fri, 7 Jul 2023 10:05:51 +0200 (CEST) Received: by lain.khirnov.net (Postfix, from userid 1000) id A65881601B2; Fri, 7 Jul 2023 10:05:50 +0200 (CEST) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: <20230707005546.GV1093384@pb2> References: <54fe8899-d250-8d62-1157-621deb546040@gmail.com> <168841533190.542.8113031316523716543@lain.khirnov.net> <4b0740-7b32-415b-47af-3199463854b@passwd.hu> <168841859463.9711.12513000520212201640@lain.khirnov.net> <20230703235057.GQ1093384@pb2> <168845004614.542.18132678959456829324@lain.khirnov.net> <20230704235012.GS1093384@pb2> <168854896467.542.3745621457505615992@lain.khirnov.net> <20230705225447.GT1093384@pb2> <168862993295.542.15593141999950137681@lain.khirnov.net> <20230707005546.GV1093384@pb2> Mail-Followup-To: FFmpeg development discussions and patches Date: Fri, 07 Jul 2023 10:05:50 +0200 Message-ID: <168871715065.542.16772150579352770511@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/hlsenc: fall back to av_get_random_seed() when generating AES128 key 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: Quoting Michael Niedermayer (2023-07-07 02:55:46) > > The litteral wording was > "that guarantees either cryptographically secure randomness or an error." > > that was what i refered to. > > the wording used now: > "to the best of our ability, and that of the underlying libraries we rely on) cryptographically secure." > > is perfectly fine with me. > I would have the same issue if someone said AES gurantees ... IMO the two formulations are equivalent whenever it comes to practical computing. An algorithm can be mathematically proven to be sound*, but any practical computing scheme on actual hardware is always subject to software bugs, system misconfiguration, hardware bugs, hardware failure, etc. We use similar wording in other documentation, where e.g. we might guarantee that some function returns a NULL-terminated string or so. That guarantee is always under the implicit condition that there are no bugs and the code runs in the expected environment. The same considerations apply here. * assuming there are no bugs in your proof -- Anton Khirnov _______________________________________________ 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".