From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/5] avcodec/mv30: Check the input length before allocation
Date: Fri, 22 Sep 2023 21:31:39 +0200
Message-ID: <CAPYw7P7wQntkCkZitiO5CK6=a8O4NppwPOUVWvK7WFR=Ah0wkA@mail.gmail.com> (raw)
In-Reply-To: <20230922192731.GD8640@pb2>
On 9/22/23, Michael Niedermayer <michael@niedermayer.cc> wrote:
> On Mon, Aug 07, 2023 at 10:22:25AM +0200, Paul B Mahol wrote:
>> NAK
>
> will apply unless you provide technical comments
NAK, never provided proof that this hack does not break decoding.
This is not really security fix.
>
> thx
>
> [...]
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Good people do not need laws to tell them to act responsibly, while bad
> people will find a way around the laws. -- Plato
>
_______________________________________________
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:[~2023-09-22 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 0:49 [FFmpeg-devel] [PATCH 1/5] avcodec/mv30: Allocate frame later Michael Niedermayer
2023-08-07 0:49 ` [FFmpeg-devel] [PATCH 2/5] avcodec/mv30: Check the input length before allocation Michael Niedermayer
2023-08-07 8:22 ` Paul B Mahol
2023-09-22 19:27 ` Michael Niedermayer
2023-09-22 19:31 ` Paul B Mahol [this message]
2023-09-22 21:34 ` Michael Niedermayer
2023-09-22 21:57 ` Paul B Mahol
2023-08-07 0:49 ` [FFmpeg-devel] [PATCH 3/5] avcodec/xvididct: Fix integer overflow in idct_row() Michael Niedermayer
2023-08-23 20:42 ` Michael Niedermayer
2023-08-07 0:49 ` [FFmpeg-devel] [PATCH 4/5] avcodec/wavarc: Check shift Michael Niedermayer
2023-08-07 0:49 ` [FFmpeg-devel] [PATCH 5/5] avcodec/wavarc: Check that nb_samples is not negative Michael Niedermayer
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='CAPYw7P7wQntkCkZitiO5CK6=a8O4NppwPOUVWvK7WFR=Ah0wkA@mail.gmail.com' \
--to=onemda@gmail.com \
--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