this post was submitted on 22 Jul 2024
30 points (94.1% liked)

Selfhosted

40347 readers
349 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

How do i you decide whats safe to run

I recently ran Gossa on my home server using Docker, mounting it to a folder. Since I used rootless Docker, I was curious - if Gossa were to be a virus, would I have been infected? Have any of you had experience with Gossa?

you are viewing a single comment's thread
view the rest of the comments
[–] Lemongrab@lemmy.one 5 points 4 months ago (2 children)

Idk how to decide what is safe or not, but as a warning, Docker containers can escape trivially and have access to the kernel.

[–] just_another_person@lemmy.world 5 points 4 months ago (1 children)

This is not true. Perhaps on an already at-risk or exploitable machine, but even then it's not trivial, and this is not a widespread thing that happens everywhere all the time

[–] kevincox@lemmy.ml 8 points 4 months ago

It is. Privilege escalation vulnerabilities are common. There is basically a 100% chance of unpatched container escapes in the Linux kernel. Some of these are very likely privately known and available for sale. So even if you are fully patched a resourceful attacker will escape the container.

That being said if you are a low-value regular-joe patching regularly, the risk is relatively low.

[–] verstra@programming.dev 2 points 4 months ago (2 children)

Can you expand on this wild claim? The whole point of containers is isolation so what you are saying is that containers fail at that all the time?

[–] asap@lemmy.world 6 points 4 months ago (1 children)

They might be talking about posts like this (which I would love to have refuted, as this kind of info has so far kept me from using Docker significantly):

https://security.stackexchange.com/a/169649

[–] ancoraunamoka@lemmy.dbzer0.com 1 points 4 months ago

There is nothing to refute, 100% correct

[–] Lemongrab@lemmy.one 0 points 4 months ago* (last edited 4 months ago)

Docker/Podman and LXC linux containers share the same kernel with the host machine. Root in the container is root period (in the case of rootfull containers). Even without root, much of the data on your machine is readable from any user. With a exploit to escape the container (which are common) the malicious program has root on the machine. This is a known attack vector against linux containers. VMs are much better for isolating untrusted software from the host OS.