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] [PATCH 2/2] avformat/concatdec: Check recursion depth
Date: Fri, 11 Jul 2025 01:36:54 +0200
Message-ID: <20250710233654.GS29660@pb2> (raw)
In-Reply-To: <aG5as7pmeV-zTUVw@phare.normalesup.org>


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

Hi Nicolas

On Wed, Jul 09, 2025 at 02:04:03PM +0200, Nicolas George wrote:
> Michael Niedermayer (HE12025-07-07):
> > a file called self_ref.ffconcat, containing:
> > 
> > ffconcat version 1.0
> > file self_ref.ffconcat
> 
> Oh, that. Thanks for explaining. I am not sure it is our responsibility
> to protect from this, there are many instance of similar pitfalls, for
> example a shell wrapper for a command with the same name that neglects
> to not call itself. But if it takes very little code like that, why
> not...
> 
> OTOH, three problem I have with the code:
> 
> ELOOP is not portable, and the message does not match the issue. It is
> better to have an error message that says nothing ("invalid value") than
> an error message that says something wrong ("symbolic links"? what
> symbolic links?).

ok, chanegd it to AVERROR_INVALIDDATA


> 
> Why do you have to implement it in concat? AFAICS, the call to
> ff_copy_whiteblacklists() should be enough to trigger the protection you
> added in patch 1/2.

Yes
but this also affects releases, and adding a field to AVFormatContext
is an issue for releases as it changes ABI

So the concat patch would go into old release branches and the
AVFormatContext one into master
Unless someone has a better idea ...


> 
> You are abusing the ff_copy_whiteblacklists() function. Since it is
> private, it can be renamed. ff_prepare_nested_muxer()?

demuxer but yes, we can rename it

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

  reply	other threads:[~2025-07-10 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 10:31 [FFmpeg-devel] [PATCH 1/2] avformat: Add recursion limit Michael Niedermayer
2025-07-07 10:31 ` [FFmpeg-devel] [PATCH 2/2] avformat/concatdec: Check recursion depth Michael Niedermayer
2025-07-07 11:05   ` Nicolas George
2025-07-07 14:58     ` Michael Niedermayer
2025-07-07 15:09       ` Nicolas George
2025-07-07 20:07         ` Michael Niedermayer
2025-07-09 12:04           ` Nicolas George
2025-07-10 23:36             ` Michael Niedermayer [this message]
2025-07-11  8:29               ` Nicolas George

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=20250710233654.GS29660@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