Great job, Hammerjack! 👏

Just as food for thought, there has also been an idea in the opposite direction - decentralize voting even more

Do you also intend to cover The Dark Mod?

Do you know of some open source scanner like that? nmap wouldn’t help back then. The problem was not an open port but configuration “inside”

For the lazy, like me: !thebazaar@lemmy.zip

Maybe https://getcroc.com/ ?

Well, then here are my thoughts and you might have missed https://piefed.zip/c/rpg@ttrpg.network/p/1909546/shadowrun-anarchy-2-0-is-out

Yes, somehow. I’m not a lawyer ;) AFAIK CGL is also just a IP licensee (from Topps IIRC?). But somehow they were able to let BBE work on SRA2

On dtrpg SRA2 is being sold as a CGL product

I’ve heard somewhere the new update has performance issues on Linux

I haven’t hosted something big in the past but I have dabbled sometimes

The ssh knockers have always been there. But now the blocklists are either more accessible or I just have heard about them more in the meantime

Scrapers did not use to DDoS so aggressively but also have been there. Now we have the challenges (anubis, cloudfront, captchas) to mitigate their hunger (and the blocklists)

What has changed is that now one needs to remember what a piece is written in. A PHP vulnerability one day, Go another. And everytime one has to run through the list “what the stuff we’re hosting is written in”. But personally, I think this will pass. What is being discovered right now are often long-standing bugs, so the only mitigation is update. Once the vulnerabilities are coming from a recent change, sometimes it will be patched before we need the newer version of a library

At first I thought you meant the electric power and was very confused

Massive shout of thanks from myself to INeedMana for jumping in and spending hours fixing this with me, guiding me, and putting up with my stress and panic!

When we were hit by scrapers the other month, both load and CPU utilization were going through the roof, server was choking even on sending ssh data. So that load of all cores being requested, while uncharacteristic, didn’t automatically feel alarming. It wasn’t that bad
When I was sitting down to take a look at the cron jobs, I was not expecting to find what we’ve found. And by the time I was getting API errors on simple docker exec I was starting to run in circles

I’m very grateful that you were there, even though it was well past midnight for you. It was much more manageable to get through that in a duo

There is a way to move a community and it should be written up in some piefed blog article. I’ve never done it yet, I’ll ask around

It’s caloric, IIRC low effort to break down and numbs feeling. No wonder the lizard brain will be dancing and singing if it has been lacking fuel for a bit

:D

That’s exactly what I would do. Including the remote repo being bare

That is my understanding too. But then when I was reading the article, there was a line somewhere that in order for the exploit to be successful, the server needs to be using eval

I used to think so too but then there was a study that any kind of stress (heating, mechanical, cooling) makes any kind of plastic release microplastics into the food. With heating being the worst, cooling “the best”

Of course I can’t find it now, I guess it might have been after the pandemic (meaning - two eternities for the way my memory works, there’s no chance I can remember what were the noticeable words in the title). But here’s something similar https://pubs.acs.org/esthag/article-abstract/57/26/9782/316425/Assessing-the-Release-of-Microplastics-and

I guess nearly everybody has installed the patch by now

I admire your belief ;)

https://php2shell.censys.com/

ATM almost 80% of scanned services are still vulnerable. Considering that **About 54% of PHP services hide their version** and are not counted as affected or patched.it doesn’t look too good

AFAIU this is not about the size of the file but making the php process that runs a file surpass the configured limit (of RAM). At which point sometimes something goes wrong with letting go of that memory and then the second vulnerability allows using that limboed memory that not only shouldn’t be used but also can contain some internal values from the first one