Selfhosted

63,680 readers

5,234 active

545 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

moderation log

moderators

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

PSA: PHP warns it plans to release 2 emergency patches imminently (today 14:00 UTC) (arstechnica.com)

submitted 2 weeks ago by BlackEco@lemmy.blackeco.com to c/selfhosted@lemmy.world

50 comments fedilink hide all child comments

The set of vulnerabilities is dubbed PHP2Shell and disclosure is scheduled for 14:00 UTC with attacks expected to follow soon after.

It is adviced to take offline every non-vital services until the patch has been installed (or the Docker image has been updated with a patched version of PHP)

Update: fix is out https://www.php.net/archive/2026.php#2026-10-21-5

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

[–] Natanox@discuss.tchncs.de 8 points 2 weeks ago* (2 children)

They took just a few hours to squeeze out a new ca-certificates. On the other hand the last time there was a huge kernel bug it took well over 24 hours I think…

permalink

fedilink

source

parent

hideshow 2 child comments

[–] slazer2au@lemmy.world 11 points 2 weeks ago

A bad ca is update a file on every pc and application. A kernal bug is way more involved so it doesn't make a new problem later.

permalink

fedilink

source

parent

[–] lemmyvore@feddit.nl 3 points 2 weeks ago

They took a lot longer than that on some past vulnerabilities, some of them sat unpatched for weeks or months. But it depends on the severity. A remote exploit of severity 9 will probably get expedited.

permalink

fedilink

source

parent