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: [FFmpeg-devel] Forensics Was: [RFC] statictrac, trac and caching
Date: Sun, 15 Jun 2025 17:58:59 +0200
Message-ID: <20250615155859.GV29660@pb2> (raw)
In-Reply-To: <34e92672-93ad-464e-a99a-125ecb1f305d@gmail.com>


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

Hi Derek

On Sun, Jun 15, 2025 at 02:53:57PM +0100, Derek Buitenhuis wrote:
> On 6/15/2025 2:42 PM, Michael Niedermayer wrote:
> > for the record, heres btw the 100 IP addresses from where the attack yesterday
> > happened: (i think timo said there where more addresses later but thats the list
> > when i looked)
> 
> These look like residential IPs from a botnet (all same ISP, so possibly compromised
> IoT device).

I hoped someone just made a honest mistake with their AI agents.

But if its a botnet
why would a botnet target ffmpegs bug tracker ?
Its expensive (in terms of computations) to solve anubis repeatedly.
A botnet is there to make some criminal a profit


> 
> Publishing these seems in poor taste.

Publishing is neccessary a first step so people can check if anyone did this
by mistake or if anyone knows where this came from.

Speaking of that. Do you have any idea, hunch or knowledge where this may
have come from ?
Or about anyone who might do this or pay a botnet operator to do this ?

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No snowflake in an avalanche ever feels responsible. -- Voltaire

[-- 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-06-15 15:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 13:35 [FFmpeg-devel] " Michael Niedermayer
2025-06-15 13:42 ` Michael Niedermayer
2025-06-15 13:53   ` Derek Buitenhuis
2025-06-15 15:58     ` Michael Niedermayer [this message]
2025-06-15 16:17       ` [FFmpeg-devel] Forensics Was: " Derek Buitenhuis
2025-06-15 14:45   ` [FFmpeg-devel] " James Almer
2025-06-15 16:13     ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer
2025-06-15 18:45   ` Michael Niedermayer
2025-06-15 14:53 ` [FFmpeg-devel] " James Almer
2025-06-15 15:57   ` Kacper Michajlow
2025-06-15 16:06     ` Marth64
2025-06-15 16:53       ` Michael Niedermayer
2025-06-15 17:03         ` Marth64
2025-06-15 16:48     ` Michael Niedermayer
2025-06-15 19:05     ` Michael Niedermayer
2025-06-15 16:28   ` 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=20250615155859.GV29660@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