Selfhosted

50550 readers

396 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Is this mail something I should be concerned about? (sopuli.xyz)

submitted 3 days ago by theselfhoster@sopuli.xyz to c/selfhosted@lemmy.world

9 comments fedilink hide all child comments

When I sshed into my server today, it said I had mail. I checked /var/mail/{myuser} and got a mail from caddy. The title was "SECURITY information for {hostname}". The message was this.

caddy : user NOT in sudoers ; PWD=/ ; USER=root ; COMMAND=/usr/bin/tee /usr/local/share/ca-certificates/Caddy_Local_Authority_-_2025_ECC_Root_31435960950297150297199787413716908247066220.crt

I'm still learning this self-hosting thing, I know enough to set stuff up but I still know barely anything about security, and the message looks kinda scary, so I would like to know what it means, thanks in advance. Note that I was messing around with Caddy and stuff yesterday, so maybe that has something to do with it, but I'm not sure.

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

[+] dgdft@lemmy.world 1 points 2 days ago* (last edited 2 days ago) (1 children)

[removed by mod]

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 day ago

If the caddy service account has write access to the config and certs, isn’t that a weaker security posture than having them owned by root?

I'm much less worried about an attacker messing w/ my certs (that's a pretty sophisticated attack) and more worried about privilege escalation where the attacker gets root access. Caddy is intended to be externally facing, so it'll be getting the brunt of the attacks (like this one that attacks HTTP 1.1). If someone is able to find an exploit to allow remote code execution, being able to run commands with sudo is a pretty big deal.

That's a big part of why I run my services in containers, and also why I'm switching from Docker to Podman. Docker runs everything as root by default, and it's a pain to run things as non-root. Podman runs everything as an underprivileged user by default, which forces the admin to configure it properly. If an attacker is able to break out of Docker, it'll have root access to the system, whereas if an attacker breaks out of Podman, they'll just have whatever that user's permission is.

If I'm going to expose something to the internet, I want to make sure it's properly configured to reduce the chances of getting a rootkit or something.