Selfhosted

63,755 readers

5,189 active

508 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

Turns out I have been updating wrong all this time! 🤦🏼 (the.unknown-universe.co.uk)

submitted 6 months ago by otter@lemmy.ca to c/selfhosted@lemmy.world

24 comments fedilink hide all child comments

I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.

Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March.

I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours is lying to you as well.

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

[–] Andres4NY@social.ridetrans.it 2 points 6 months ago (2 children)

@GreenKnight23 @oong3Eepa1ae1tahJozoosuu I've never seen that behavior in Debian. Is that some different type of configuration?

permalink

fedilink

source

parent

hideshow 2 child comments

[–] GreenKnight23@lemmy.world 2 points 6 months ago (1 child)

native config. nothing special.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Andres4NY@social.ridetrans.it 2 points 6 months ago

@GreenKnight23 I don't see that behavior. Rebooting into a new kernel and then running dist-upgrade, it always always keeps one older kernel around. Bookworm and trixie.

permalink

fedilink

source

parent