This issue is already quite widely publicized and quite frankly โ€œweโ€™re handling it and removing thisโ€ is a much more harmful response than I would hope to see. Especially as the admins of that instance have not yet upgraded the frontend version to apply the urgent fix.

Itโ€™s not like this was a confidential bug fix, this is a zero day being actively exploited. Please be more cooperative and open regarding these issues in your own administration if youโ€™re hosting an instance. ๐Ÿ™

You are viewing a single thread.
View all comments View context

I think the authoritative source should be the GitHub repo. A security advisory should be posted there with references to outside resources as necessary.

permalink
report
parent
reply
1 point

checks all the boxes - authoritative (authenticated user accounts), central location, not on fediverse, already relatively well-known by lemmy users and provides visibility to remediation. Itโ€™s a good idea.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you donโ€™t control.

Rules:

  1. Be civil: weโ€™re here to support and learn from one another. Insults wonโ€™t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If itโ€™s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Donโ€™t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (donโ€™t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.1K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments