From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/4] avformat/hls: Some extension fixes that need testing
Date: Sun, 6 Apr 2025 15:43:55 +0200
Message-ID: <20250406134355.GG4991@pb2> (raw)
In-Reply-To: <7e33746e-5772-4f82-87b1-7fa0ebbd9f09@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1198 bytes --]
Hi
On Sun, Apr 06, 2025 at 09:20:58AM -0400, Leo Izen wrote:
> On 4/6/25 7:16 AM, Michael Niedermayer wrote:
> > Hi all
> >
> > This patchset adds all the extensions i found on trac and its links to
> > allowed_extensions for hls.
> > There was one testcase only so most of this is untested. It may be
> > needed to add the extensions also to demuxers or as exceptions
> > specific to hls elsewhere.
> >
>
> If the issue at hand is that bad extensions can cause invalid
> demuxers/decoders to be probed, why don't we just use a demuxer or decoder
> whitelist? We already have code to support this.
The issue at hand is that i have no testcases.
People either post testcases for 3rd party tools not for FFmpeg
or dead links or half m3u8 files
I could also say the issue is that we have noone like carl who
replied to users and asked for full replicatable bug reports.
Once we have replicatable testcases, we can discuss which is the
smartest way to fix them.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If you think the mosad wants you dead since a long time then you are either
wrong or dead since a long time.
[-- 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".
prev parent reply other threads:[~2025-04-06 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 11:16 Michael Niedermayer
2025-04-06 11:16 ` [FFmpeg-devel] [PATCH 1/4] avformat/hls: Add cmfv and cmfa to allowed_extensions Michael Niedermayer
2025-04-06 11:16 ` [FFmpeg-devel] [PATCH 2/4] avformat/hls: Point user to how to easily contribute a fix for missing extensions Michael Niedermayer
2025-04-06 11:16 ` [FFmpeg-devel] [PATCH 3/4] avformat/hls: Add ec3 to allowed_extensions Michael Niedermayer
2025-04-06 11:16 ` [FFmpeg-devel] [PATCH 4/4] avformat/hls: add fmp4 " Michael Niedermayer
2025-04-06 13:20 ` [FFmpeg-devel] [PATCH 0/4] avformat/hls: Some extension fixes that need testing Leo Izen
2025-04-06 13:43 ` Michael Niedermayer [this message]
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=20250406134355.GG4991@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