Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 8.0 Release
Date: Wed, 23 Jul 2025 19:48:51 +0200
Message-ID: <20250723174851.GM29660@pb2> (raw)
In-Reply-To: <0E79640C-B2A7-4C81-9618-CEEC09357668@unified-streaming.com>


[-- Attachment #1.1: Type: text/plain, Size: 1776 bytes --]

On Wed, Jul 23, 2025 at 06:43:51PM +0200, Dimitry Andric wrote:
> On 23 Jul 2025, at 18:27, Michael Niedermayer <michael@niedermayer.cc> wrote:
> > 
> > On Wed, Jul 23, 2025 at 03:45:28PM +0200, Timo Rothenpieler wrote:
> >> On 23/07/2025 13:43, Michael Niedermayer wrote:
> >>> Hi everyone
> >>> 
> >>> I intend to create the release/8.0 branch in the next 1-2 weeks
> >>> after that i intend to make teh 8.0 release in the following 1-2 weeks
> >>> 
> >>> If theres something you want in it make sure its pushed before the branch
> >>> is made.
> >> 
> >> Would it be sensible to enable tls verify by default with 8.0?
> >> Or would that have to go through a longer "deprecation" period?
> >> 
> >> We've just added proper verification support to openssl, schannel and other
> >> backends already had it.
> >> It's just default-disabled for some reason.
> >> IMO it'd make sense to turn it on by default, it has surprised me and other
> >> people in the past that FFmpeg does not verify TLS certificates in any way
> >> by default.
> > 
> > Is there some disadvantage ?
> > 
> > if not i would suggest to enable it
> 
> As long as there is a command line option to disable checking, it should
> be a good default.

> There are many sites out there with badly configured
> certificates, or self-signed ones, which would no longer work, otherwise.

the fix for this is to check crt.sh

example: https://crt.sh/?q=ffmpeg.org

and if there are or where correct certificates, reject the self signed one
otherwise allow self signed by default with a warning

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Everything should be made as simple as possible, but not simpler.
-- Albert Einstein

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

  reply	other threads:[~2025-07-23 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 11:43 Michael Niedermayer
2025-07-23 13:45 ` Timo Rothenpieler
2025-07-23 16:27   ` Michael Niedermayer
2025-07-23 16:43     ` Dimitry Andric
2025-07-23 17:48       ` Michael Niedermayer [this message]
2025-07-23 18:19         ` Jacob Lifshay
2025-07-24  0:16           ` Michael Niedermayer
2025-07-23 18:40         ` Nicolas George
2025-07-23 23:58           ` Michael Niedermayer
2025-07-23 14:01 ` Niklas Haas
2025-07-23 14:01   ` Niklas Haas
2025-07-24  0:38     ` James Almer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250723174851.GM29660@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git