this post was submitted on 19 Apr 2025
98 points (100.0% liked)
Technology
38565 readers
153 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It downloads things without checking signatures by default. And even if you enable DCT, it TOFUs every key without even asking or checking against a WoT
Basically, using docker means you could run malicious code (arbitrary code execution) in your container because it doesn't verify what it downloads.
The bright side is, that you run it in a container. Beware of privileged mode, don't give it unnecessary mounts or networks, and there's very little some malicious code can do.
If you're using it for a build system, tough luck but you need to manage the keys to avoid TOFU, and ideally pull from your own registry.
A container that has access to all the data on the database. All the users data is compromised. And the attacker can execute malicious JavaScript on the users.
There's nothing bright about using docker. Its a huge risk.