From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <jamrial@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] web/security: what not to post to ffmpeg-security
Date: Tue, 11 Nov 2025 22:41:49 -0300
Message-ID: <c1856703-0fe5-43f8-80ec-5e0ed87fad79@gmail.com> (raw)
In-Reply-To: <20251112014014.801600-1-michael@niedermayer.cc>
[-- Attachment #1.1.1: Type: text/plain, Size: 846 bytes --]
On 11/11/2025 10:40 PM, Michael Niedermayer via ffmpeg-devel wrote:
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
> src/security | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/security b/src/security
> index 0d5f8dd..65b25bc 100644
> --- a/src/security
> +++ b/src/security
> @@ -1,4 +1,4 @@
> -<p>Please report vulnerabilities to <a href="mailto:ffmpeg-security@ffmpeg.org">ffmpeg-security@ffmpeg.org</a></p>
> +<p>Please report vulnerabilities to <a href="mailto:ffmpeg-security@ffmpeg.org">ffmpeg-security@ffmpeg.org</a>. Note, we have recently seen a spike in false positives. Make sure that what you report are real issues either by providing a PoC or by carefull human verification.</p>
"careful".
LGTM otherwise.
>
> <h2>FFmpeg git master</h2>
> <p>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-12 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 1:40 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-12 1:41 ` James Almer via ffmpeg-devel [this message]
2025-11-12 2:27 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
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=c1856703-0fe5-43f8-80ec-5e0ed87fad79@gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jamrial@gmail.com \
/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