Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] vvcdec: Mark as experimental
Date: Thu, 8 Feb 2024 18:16:19 +0000
Message-ID: <CAK+ULv6uOwhRUJGoHtrhwaSL7pBh2+HG7TbwHJt0B9pd2bzs_g@mail.gmail.com> (raw)
In-Reply-To: <CAFXK13dowtiP08q=BtVrpSPfPGeK7vLUp9=iF+nszZbaBffXDQ@mail.gmail.com>

On Thu, 8 Feb 2024 at 06:01, Nuo Mi <nuomi2021@gmail.com> wrote:

> On Thu, Feb 8, 2024 at 6:55 AM Kieran Kunhya <kierank@obe.tv> wrote:
>
> > On Wed, 7 Feb 2024 at 22:06, Paul B Mahol <onemda@gmail.com> wrote:
> >
> > > On Wed, Feb 7, 2024 at 10:13 PM Kieran Kunhya <kierank@obe.tv> wrote:
> > >
> > > > $subj
> > > >
> > > > As discussed at FOSDEM.
> > > >
> > >
> > > Author of this patch above is forced to FUZZ this decoder until
> > > experimental flag is removed.
> > >
> >
> > Sure, I will set some fuzzers up over the weekend.
> >
> Better add something here
> https://ffmpeg.org/developer.html#New-codecs-or-formats-checklist to
> explain to people what kind of new codecs should be treated as experimental
> and how they can graduate from experimental status.
>

Hi Nuo,

Sure, this isn't saying your incredible work is bad. It's just the reality
that a complex codec needs to be fuzzed heavily otherwise the security
community will report FFmpeg 7.0 has a ton of security issues.

Regards,
Kieran Kunhya
_______________________________________________
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:[~2024-02-08 18:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 21:13 Kieran Kunhya
2024-02-07 22:06 ` Paul B Mahol
2024-02-07 22:55   ` Kieran Kunhya
2024-02-08  6:00     ` Nuo Mi
2024-02-08 18:16       ` Kieran Kunhya [this message]
2024-02-09  3:54         ` Nuo Mi
2024-02-13  2:56           ` Nuo Mi
2024-02-14  2:57             ` Nuo Mi
2024-02-14  9:41               ` Kieran Kunhya
2024-03-14 22:54     ` Michael Niedermayer
2024-03-15 10:22       ` Kieran Kunhya
2024-03-15 15:00         ` Frank Plowman
2024-03-15 15:04           ` Andreas Rheinhardt
2024-03-16 14:50             ` Nuo Mi
2024-03-16 14:49           ` Nuo Mi
2024-02-14 11:49 ` Andreas Rheinhardt
2024-02-14 13:41   ` Kieran Kunhya
2024-03-13 21:34     ` 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=CAK+ULv6uOwhRUJGoHtrhwaSL7pBh2+HG7TbwHJt0B9pd2bzs_g@mail.gmail.com \
    --to=kierank@obe.tv \
    --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