Lionir elected to prevent any potential data leaks by shutting down Beehaw until the issues lemmy.world and lemmy.blahaj.zone are identified and resolved
Funnily enough, beehaw was the most protected from this vuln, as their more stringest application requirements made it unlikely the attacker got in. It also didn’t affect lemmy.dbzer0.com even though our application form is much simpler than theirs.
I’m not on Beehaw, but it seems well run based on the decisions they make and who they let in.
They’re very consistent and predictable in a very good way. I understand the desire to have a more permissive instance at the cost of dealing with some trolls, but I think beehaw does an excellent job of delivering a community that takes the health and safety of the community at large seriously
For the best. Knowing that this hacking technique is a vulnerability with the Lemmy project as a whole, I think it’s reasonable for instances to temporarily close while a fix is implemented.
How do we know that?
Edit: Seems like https://github.com/LemmyNet/lemmy-ui/pull/1897/files
Attack vectors reduced to 0
Does anyone have an article about the vulnerability itself?
They’re not telling (rightfully so) and hopefully won’t until all instances are fixed.
now thats how you protest
