• 4 Posts
  • 127 Comments
Joined 2 years ago
cake
Cake day: July 12th, 2024

help-circle

  • I feel like I read the exact same story (Person discovers docker group is effectively root because llm agent used it to circumvent not having sudo) a few minths ago. (Not saying you stole it, two people can have the same experience independently of each other. I just found it interesting that this is, apperently, such a commonly overlooked issue.)

    Also, this is documented:

    Running containers (and applications) with Docker implies running the Docker daemon. This daemon requires root privileges unless you opt-in to Rootless mode, and you should therefore be aware of some important details.

    First of all, only trusted users should be allowed to control your Docker daemon. This is a direct consequence of some powerful Docker features. Specifically, Docker allows you to share a directory between the Docker host and a guest container; and it allows you to do so without limiting the access rights of the container. This means that you can start a container where the /host directory is the / directory on your host; and the container can alter your host filesystem without any restriction. This is similar to how virtualization systems allow filesystem resource sharing. Nothing prevents you from sharing your root filesystem (or even your root block device) with a virtual machine.

    https://docs.docker.com/engine/security/#docker-daemon-attack-surface





  • Just out of curiosit, what do you gain from unmounting the fs? Depending on your reasoning, it might he an option to use a zfs filesystem, set it up so automatic jobs rarely run and then set a somewhat agressive disk spin down policy. That way fs info would be handled by the arc, not the disks and they would only spin up when an actual file is accessed.

    At least I assume it would work this way. Look-Ahead reads or your explorer generating previews, etc. might well make thta option fail.





  • For professionals and buisnesses, I see where you are coming from (although there is an argument to be made for prioritizing security over uptime whenever acceptable).

    But for selfhosting/private users? If I wake up one morning and my stuff is not working anymore, I can just roll back to the last good backup and then apply patches manually to see where it goes wrong. Way better to have some downtime when I don’t notice (i.e. don’t need the service) than having open vulnerabilities when a fix exists.



  • It seems like the choice was not made out of mallice, but legal obligations (reply stolen from reddit):

    2026-09-21 - Update by Qobuz support: Hello, thank you for your message.

    Following the recent changes made to the QBZ repository, we’d like to provide some clarifications regarding this decision.

    QBZ was an independent application developed by a third party and was not developed, maintained or distributed by Qobuz. We know that QBZ was a really convenient solution for our Linux users.

    However, we have strict legal and contractual obligations toward rights holders to ensure fair artist compensation. Unfortunately, the app placed Qobuz in a non-compliant position, which left us no choice but to ask the developer to stop its distribution.

    The use of the unoffical app unfortunately leads to streams not being counted with us and thus the artists end up empty-handed.

    We completely understand that this situation is frustrating for the Linux community. This was a difficult decision, but it’s necessary to protect both artists and our platform.

    We are actively working on releasing an official Linux application as soon as possible. Thank you for your patience and understanding in the meantime.

    Kind regards,

    Marina

    Qobuz

    I agree with the comments here, that this could have been handled better, providing an open API that ensures streams are counted, taking over or building on qbz to release their own client, etc. But I think this is not an issue with Qobuz, but moreso with the music industry.

    Anyhow, I guess I’ll get a seedbox subscription instead now :/.



  • Are the parties young people have nowadays just less wild because everyone has cameras?

    I believe so.

    Is this why Gen Z thinks hedonism is cringe?

    I think part of it might be the (reasonable) fear of being caught and it haunting you forever increasing overthinking. But I think the main reason is excessive access to everything online desensitizing and removing the enicing part of exploring ‘taboo’ stuff. Under that aspect I think, the internet as we have it today has also just reduced curiocity overall.

    I think a more significant part though is that sex, drugs and the like are just not that taboo anymore. You are not hooking up as an act of rebelion against your parents if your parents lived hookup culture and are open about it.

    And a lot of us are just more lonely/less social which loops back to the original post I guess.