Beehaw Support

153 readers

2 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our July 2023 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

Important Notice: Possible security incident - no detected impact (beehaw.org)

submitted 1 year ago by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

Between 19:45 UTC and 19:50 UTC, there was a mistake in how information was stored temporarily (cached) on Beehaw. This mistake could have allowed some people to see and use other people's accounts without permission.

If you were using the website during that time, please check that your account settings and email address are still correct. Also, make sure that any posts or actions you made during that time are still connected to your account.

It's important to note that we don't have any proof that this error was actually used by anyone to do anything bad during the short time it happened.

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

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (2 children)

Thanks for working through these issues and improving performance of the website! Very appreciated. I've been tempted recently to create my own Lemmy instance, was this a problem with an nginx configuration option? How much does Beehaw deviate from a standard Lemmy deployment?

Feel free to answer vaguely if you don't feel comfortable with giving away the details : )

[–] [email protected] 7 points 1 year ago (2 children)

was this a problem with an nginx configuration option?

Basically, this was proxy_cache_key being configured incorrectly. If you don't use the proxy_cache you should be fine.

The only thing we changed from the norm is ulimits and some nginx settings. If we figure out what works well, we'll probably create a post about how to host lemmy. If you stick to the defaults, you'll be mostly fine if your instance isn't as big as Beehaw's.

[–] [email protected] 3 points 1 year ago

Awesome! Thanks for the response. I'd love a post sometime on hosting Lemmy. I'd find it very interesting and useful!

[–] [email protected] 2 points 1 year ago (1 children)

Im also considering to setup nginx caching for lemmy.ml. Did you find a configuration which works?

[–] [email protected] 3 points 1 year ago (1 children)

Not yet. Session tracking in Lemmy is pretty hard to proxy, I'll have to dive into the code to figure out why.

[–] [email protected] 2 points 1 year ago

Have a look at this: https://github.com/LemmyNet/lemmy-ansible/pull/75

Sending proper cache-control headers from Lemmy will require some big code changes though.

[–] [email protected] 3 points 1 year ago

Yes.

Deviation is pretty minimal, related to configuration and customization.