RetroFed Forums
Your home away from modern life.
Search Categories Forum list Register Log in
About RetroFed
RetroFed

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

  • Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
  • Communities need to be Retro or Retro-adjacent.
  • Please don't upload pornographic content. (use an external image host for that)
72 registered users
Administrators: DosDude, Die4Ever
Visit retrofed.com
PSA: PHP warns it plans to release 2 emergency patches imminently (today 14:00 UTC)
Post Reply RetroFed Forums Forum Index » Selfhosted
Page 2 of 2   Goto page « First 1, 2
AuthorMessage
hereiamagain sh.itjust.works hereiamagain@sh.itjust.works
Joined: 2025-08-15
#52 · Quote Reply
GreenKnight23 wrote:
Should I take it down? depends. do you want to deal with a simple patch in 24 hours or do you want to rebuild an entire legacy system from nothing (assuming you don't take proper backups)?

How dare you (correctly) assume I haven't taken proper backups!

Jk lol

I do have a couple backups I made a few months ago. Never tested restoring them, so I don't count them as "real".

I'm hosting on namecheap servers, using their cpanel and stuff. So I don't have the option of installing my own PHP version, just selecting theirs.

But apparently they had some mitigations in place before updating, and then they got us updated.
2
communism lemmy.ml communism@lemmy.ml
Joined: 2024-03-19
#53 · Quote Reply
IanTwenty wrote:
They didn't move fast enough on it and others began circulating it. So they had to play catch up, hence the need to react before they had a patch. We won't pretend otherwise: the delay was a structural failure, caused by both the security team's decision process and its lack of resources. The security team has since started changing its processes, and that work continues, so that decisions can ...

Wow, this article really reads as LLM-generated to me. The quoted section with the "We won't pretend otherwise:", the second paragraph in:

This post isn't about how to update. It's about how these vulnerabilities were found and fixed, what has changed in how PHP security is handled over the past two years, and what we need from the organizations that depend on PHP to keep PHP's security work going.

Could they not be bothered to write a write-up about such a critical severity?
2
Post Reply Page 2 of 2   Goto page « First 1, 2
Back to top
Powered by RetroFed · PieBB frontend · All times are Europe/Amsterdam