News for hackers. Stuff that matters.
Re:The sad state of sysadmin in the age of containers (2015) by hvidgaard on Monday December 09, 2019 @07:18AM (#21741987)
If you can build on your distro of choice, you can rely on the same security audit and process. Keep track of the packages you link against and include in your image, and just rebuild your images when a new security update comes along. Then you replace the running one.
Re:The sad state of sysadmin in the age of containers (2015) by dsr_ on Monday December 09, 2019 @07:58AM (#21742188)
See that "keep track" bit? It's expensive unless you build a tool to do it for you -- which is what I said previously.
Re:The sad state of sysadmin in the age of containers (2015) by hvidgaard on Monday December 09, 2019 @09:49AM (#21743077)
Pulling the list of security updates is trivial. And during development you'll know what you depend on. Comparing the two in a script is trivial.

But regardless, with containers, it should be a setup where you can rebuild your images daily with all the latest security fixes. Or whenever there is a fix you deem important.

Re:The sad state of sysadmin in the age of containers (2015) by adamtulinius on Monday December 09, 2019 @09:59AM (#21743157)
You don't have to keep any more track than you do with your OS; it's just a different button you hit when updating containers.

Or don't keep track at all: Just rebuild and redeploy often enough.

Re:The sad state of sysadmin in the age of containers (2015) by grosswait on Monday December 09, 2019 @10:21AM (#21743346)
Except the OS is one place, one org. With containers it could exponential.
Re:The sad state of sysadmin in the age of containers (2015) by dsr_ on Monday December 09, 2019 @10:16AM (#21743298)
Supply chain attackers love this.