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 13FB74502F for ; Wed, 28 Dec 2022 16:30:46 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id B418F68B9DC; Wed, 28 Dec 2022 18:30:44 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 7353868016E for ; Wed, 28 Dec 2022 18:30:38 +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 2BSGUb1J003333 for ; Wed, 28 Dec 2022 17:30:38 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id BD74EEB5B7; Wed, 28 Dec 2022 17:30:37 +0100 (CET) Date: Wed, 28 Dec 2022 17:30:37 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20221227214033.GS3806951@pb2> 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]); Wed, 28 Dec 2022 17:30:38 +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="===============3425696536872744939==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============3425696536872744939== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="l9YnVAW68Uyny6u6" Content-Disposition: inline --l9YnVAW68Uyny6u6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mark Gaiser (12022-12-28): > > Ok, that made me laugh :) I did not write that. And that feels rude. > Please correct me as I'm probably wrong. > But where did anyone say that there was a working alternative solution th= at > did not require customizing how ffmpeg is used? > Like disabling safe. Heuristics to not require safe in cases where it is quite safe would be much more acceptable than a redundant ad-hoc format. --=20 Nicolas George --l9YnVAW68Uyny6u6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmOsbysACgkQcZVLI8pN xgxvEBAArTIqqI8kZYsM0ogpSgG/j1xLaPawFNtCjTy4c0PYU2DerEQoQSSQKAVz 1NTvjS/wNNAM57dMhGaqI3oMMWMUHHFKslH97Jk9LEcraXRStH4SYGd6rqQeH6E1 gRxFClBHKewLWWgCvELFFVYxqw/BnG621ShW8PUD9SiCe7f2h8wjR8VgdfGP3M6a Ro3h9lrC/Ld4OA9TnNPQE/aFh8g3nWNaCyUPRH9dfw7Y5Lv0I1X3cTStTWajjrjs dKVDAnq2w2VBDxrWZNBJlB8Ap9w8okac6uL+pqOuOw4CftSG717aOSaTdoiKKF+y HDaZdR9dVjOyF5Oa5pEhqKAL5ywMApfp9Gq9+YT1gYrkh2M1sbnMstjYRW5bYfdF kyzIPAxFCsbQSUKJuNei5Pflpfg03Hjs2jFPPIvNnfhFyYMjC83CwlghjozK1KXJ nEV115LQLqFbEo2emzsHsuGdYxPEfAA6wTl+M81yF+EH/qTtLjISSaRPrrUifDJa yGre9JqRYl6ZffSo2KHygt1lxlfbYzIWZFjxLwC76krLf220KhKp3voe9xdia6Rq XPJ6l4eymqaCg1xQ7wWw3lpR+d3Sm+i+I8w4zJjo7iNTfjEjHeX7cYNGhvbfO6Ri wGkTHA7T9R9nhYTGHFRXV7QEzx8MV91TWqF6WpZPIS+aibgnnNs= =CSLf -----END PGP SIGNATURE----- --l9YnVAW68Uyny6u6-- --===============3425696536872744939== 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". --===============3425696536872744939==--