Important Notice: Possible security incident - no detected impact

3 years ago by PenguinCoder to c/support

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.

load all comments
Cougar 6 points 3 years ago

Do we know what could have caused this cache error?

path: 0 6277, hotness: undefined, score: 6, children: 10
Penguincoder 10 points 3 years ago

Yes; configuration settings for the web server involving improving performance. Those settings have been changed back to the previous, non-issue ones. So this should not occur at this time, or again.

path: 0 6277 6287, hotness: undefined, score: 10, children: 9
Cougar 10 points 3 years ago

Is this a mistake that's easy to do for an inexperienced instance admin or just a consequence of too much fiddling and shouldn't be an issue for other instances?

path: 0 6277 6287 6327, hotness: undefined, score: 10, children: 8
support
support

@beehaw.org

login for more options
153
277
1

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.

go to feed...