From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg 8.0 Release
Date: Wed, 23 Jul 2025 15:45:28 +0200
Message-ID: <f1b632d9-fdf1-4a48-a05c-8cfe9b72dcc8@rothenpieler.org> (raw)
In-Reply-To: <20250723114343.GK29660@pb2>
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.
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-23 13:45 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 [this message]
2025-07-23 16:27 ` Michael Niedermayer
2025-07-23 16:43 ` Dimitry Andric
2025-07-23 17:48 ` Michael Niedermayer
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=f1b632d9-fdf1-4a48-a05c-8cfe9b72dcc8@rothenpieler.org \
--to=timo@rothenpieler.org \
--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