Elvith Ma'for

Former Reddfugee, found a new home on feddit.de. Server errors made me switch to discuss.tchncs.de. Now finally @ home on feddit.org.

Likes music, tech, programming, board games and video games. Oh… and coffee, lots of coffee!

I � Unicode!

  • 0 Posts
  • 41 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2024

help-circle




  • Ironically that won’t help. Email is unencrypted and you’re not allowed to send “sensible data” over it as it would be violating the GDPR.

    On the other side you’re technically not allowed to use a fax machine for that either as the recipient might forward faxes to an email inbox and that’d be unencrypted.

    But nobody talks about fax being unencrypted either… Also the argument for fax is that POTS is a direct connection between two fax machines while the internet wouldn’t be and were easier to eavesdrop on. Since everything is SIP nowadays,… But I don’t know what they’re thinking besides “we’ve done that for all those years why wouldn’t it work now?”



  • What about this? This basically forbids you to fork the software if you want to - e.g. because they’re maybe going closed source in a few years?

    You may not use the Software, in whole or in part, to create, distribute, or operate any product, system, or service whose primary function directly overlaps with or replicates the core business purpose of the Product, unless explicitly authorized in writing by fabricators.





  • The docker daemon runs as root. And as such, it can access anything initially. If your container doesn’t explicitly (or implicitly) change the uid or drops capabilities, the container also runs as root (ok, IIRC some capabilities are always dropped, but the container stays almost root). It’s still locked in its own little sandbox, but the mounting of those paths etc. happens with root.

    If you enter a docker command (docker run ..., docker build ..., …) this command will not run the containers by themselves, but instead call said docker daemon (that is running as root) by using a socket (/var/run/docker.sock).

    To only allow trusted users to interact with the docker daemon, this socket can only be accessed by root or by users in the docker group. That’s why you usually need to type sudo docker run.... Sadly many tutorials tell you to just blindly add your user to the docker group so that you do not need to use sudo to interact with docker. BUT that now means that you gave you or those users basically full access to your whole filesystem (and thus system configuration) without sudo. Any programs (or viruses or AI Agents or…) running with these user accounts also get this group and thus docker’s capabilities.

    That’s why you should NEVER add your user to the docker group or enable passwordless sudo, as you’re just one simple command/tool/script/prompt/… away from a privilege escalation.

    You can configure docker to run rootless with only your user’s capabilities and rights, but at that point… Why configure docker to do something that other docker compatible projects like Podman offer out of the box?




  • Another thing Claude tried to do on my coworker’s machine yesterday was basically:

    ✨ Yes, that is easy, let me just generate a systems unit file for you…

    [Generates file]

    Should I install that unit now for you?

    Yes

    Alright, let me do that for you

    [Saves file]

    [Tries to run systemctl daemon reload]

    [Tries to activate the unit]

    It looks like I have insufficient rights to proceed, let me try another way…

    docker -rm -v /etc/systemd/system:/mount:Z -v ./unitfile.service:unit file.service:Z alpine /bin/sh cp ./unitfile.service /mount/

    Here, I installed the unit for you!