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: Thu, 24 Jul 2025 01:58:42 +0200
Message-ID: <20250723235842.GN29660@pb2> (raw)
In-Reply-To: <aIEslsfa6_fCDEXE@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 2224 bytes --]
On Wed, Jul 23, 2025 at 08:40:22PM +0200, Nicolas George wrote:
> Michael Niedermayer (HE12025-07-23):
> > 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
>
> “502 Bad Gateway”
there are others like
https://osint.sh/crt/
> I doubt it can be a fix for anything.
>
> Anyway, that cannot be a fix:
> - the site could get compromised;
I think modifying these logs in an undetectable way is cryptographically not simple
https://certificate.transparency.dev/howctworks/
> - our users might not trust them;
The "Certificate Transparency" ? there should be no trust involved here.
Its just an append only log of all certificates
If you meant that the user might not trust a self signed certificate,
even if there never was a better certificate, then the user cannot
access the url in question if thats the only certificate the target url
provides
> - the site could be down;
thats detectable and then no self signed certificate would be accepted by default
> - internet access might not be available;
thats detectable and then no self signed certificate would be accepted by default
> - the extra latency might be unacceptable;
agree
but note, this was a somewhat hypothetical suggestion. I think its an interresting
idea. I dont expect anyone is going to just implement it like this.
The shit performance of these public sites is one problem that would need to be
solved first
> - …
>
> And it is our users' absolute right to access sites with self-signed or
> invalid certificate, starting with sites they operate themselves in test
> environments, without the say-so of any other site.
agree but that should not be default for a https url.
People today expect https to be secure
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Whats the most studid thing your enemy could do ? Blow himself up
Whats the most studid thing you could do ? Give up your rights and
freedom because your enemy blew himself up.
[-- 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".
next prev parent reply other threads:[~2025-07-23 23:58 UTC|newest]
Thread overview: 31+ 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
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 [this message]
2025-07-23 14:01 ` Niklas Haas
2025-07-23 14:01 ` Niklas Haas
2025-07-24 0:38 ` James Almer
2025-07-25 15:34 ` Andrew Randrianasulu
2025-08-19 20:06 ` Michael Niedermayer via ffmpeg-devel
2025-07-25 15:50 ` Derek Buitenhuis
2025-08-01 22:17 ` Jacob Lifshay
2025-08-19 21:10 ` Michael Niedermayer via ffmpeg-devel
2025-08-01 23:16 ` Romain Beauxis
2025-08-19 21:13 ` Michael Niedermayer via ffmpeg-devel
2025-08-20 1:18 ` Lynne via ffmpeg-devel
2025-08-20 21:06 ` Michael Niedermayer via ffmpeg-devel
2025-08-21 15:33 ` Kacper Michajlow via ffmpeg-devel
2025-08-02 9:05 ` Niklas Haas
2025-08-02 9:19 ` Nicolas George
2025-08-04 8:13 ` Tobias Rapp
2025-08-04 8:16 ` Nicolas George
2025-08-06 5:47 ` Rémi Denis-Courmont
2025-08-08 16:45 ` Michael Niedermayer
2025-08-17 8:09 ` Rémi Denis-Courmont via ffmpeg-devel
2025-08-08 16:43 ` Michael Niedermayer
2025-08-08 23:24 ` Romain Beauxis
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=20250723235842.GN29660@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