Announcements and Meta

99 readers

2 users here now

A community reserved for communications from the Based Count admin team to its users.

Occasionally we will also hold community polling in here. Make sure to subscribe to not miss any updates.

Everyone is welcome to join the discussion! We accept suggestions on how to run the instance from everybody, including users from other instances.

Posting to this community is restricted to the admin team to avoid spam, however feel free to speak your mind about the status of the instance and how you'd improve it in our !general@lemmy.basedcount.com community.

founded 2 years ago

MODERATORS

Nerd02@lemmy.basedcount.com

Atalocke@lemmy.basedcount.com

Coda@lemmy.basedcount.com

AutoMod@lemmy.basedcount.com

Transparency report: broken images and federated CSAM attack (lemmy.basedcount.com)

submitted 2 years ago* (last edited 2 years ago) by Nerd02@lemmy.basedcount.com to c/announcements@lemmy.basedcount.com

15 comments fedilink hide all child comments

Images posted within the last 48 hours will appear as broken. This is expected and intended.

Yesterday 2023-08-27 a community on the lemmy.world instance received multiple posts containing CSAM (or as it is more commonly known CP) content, which spread throughout the federation. We also ended up becoming involuntary hosts of said content.

Due to the severely limited nature of the Lemmy moderation tools, removing or purging the incriminated posts from the admin UI wasn't sufficient and didn't cause the images to be actually removed from our server. Because of this, a nuclear option was required. I have deleted every image saved by our server during the last 48 hours.

Unfortunately this also includes a post on !pcm@lemmy.basedcount.com , as well as multiple posts on !returntomonke@lemmy.basedcount.com. Authors of the affected posts can fix them by re-uploading their images, without the need to recreate the posts.

We are sorry for the inconvenience, but hosting CSAM content is highly illegal and we simply can't take any risks on this front.

I am currently discussing with the other admins whether further measures are necessary, to prevent this from happening in the future. We'll keep you posted if we have any updates.

EDIT [2023-08-28 10:00 UTC]:

The attack is still ongoing. I have now blocked the community and further deleted the last 15 minutes of images.

you are viewing a single comment's thread
view the rest of the comments

[–] betwixthewires@lemmy.basedcount.com 5 points 2 years ago (7 children)

Lemmy needs an option for admins to not cache federated media, and only deliver it from it's originating instance on request. That way, the offending server can handle it or be defederated if theyret complicit without this systemic, network wide cleanup job, it's a huge security vulnerability to the network as a whole.

[–] Nerd02@lemmy.basedcount.com 3 points 2 years ago* (last edited 2 years ago) (6 children)

Yeah good points.

not cache federated media

That's actually likely to come in the next update (pull request). It actually was proposed as a measure to save space, rather than to fix a security issue, but it do nonetheless.

only deliver it from it’s originating instance on request

Don't think I agree with this. It's not so easy as an admin to identify contents of this kind getting posted on your instance or knowing that you have trolls among your userbase. It's the kind of stuff that is hard to predict and once it's happened it's already too late. As an alternative I would propose:

fix the damn "purge" button: we actually do have a button to delete content off the database on the admin interface. Only thing is, it doesn't currently cover image caches, those stay indefinitely unless manually deleted from the terminal, as I did today. This is a MAJOR flaw and should be fixed ASAP
someone in the admin matrix chat proposed federated purges. It's somewhat controversial, but basically means that the content would get automatically deleted on all instances if the admin of the instance where it was originally posted presses the purge button. That way the lemmy.world admin could have automatically solved the problem for every other instance.

[–] betwixthewires@lemmy.basedcount.com 0 points 2 years ago* (last edited 2 years ago) (1 children)

The two quotes of mine are functionally equivalent. Not caching data and delivering from the source on request are the same thing.

[–] Nerd02@lemmy.basedcount.com 1 points 2 years ago* (last edited 2 years ago)

From the way you worded it I understood it as:

I get the option to not cache images posted by anyone else
you get the option to prevent me from caching your content

which aren't the same thing, two different people making the same choice

load more comments (4 replies)