Re:Podman Desktop v1.5 with Compose onboarding and enhanced ...
by bildiba on Friday November 03, 2023 @06:53PM
(#38136129)
Even more so if said containers contain Trojans.
Bit more secure than running directly, but if the container is broken out of, attacker directly gets root.
Re:Podman Desktop v1.5 with Compose onboarding and enhanced ...
by mmh0000 on Friday November 03, 2023 @11:38PM
(#38137942)
Adding to the parent's point. The docker hub is full of malware images and the docker devs could not care less.1.2.3.
1. https://www.bleepingcomputer.com/news/security/docker-hub-re...
2. https://sysdig.com/blog/analysis-of-supply-chain-attacks-thr...
3. https://www.bleepingcomputer.com/news/security/thousands-of-...
Re:Podman Desktop v1.5 with Compose onboarding and enhanced ...
by heresie-dabord on Saturday November 04, 2023 @10:55AM
(#38141577)
It's often the case with software "repositories". Pypi, npm, Maven... Security is expensive.
An organisation needs money, on-staff security professionals, and (of course) lawyers to explicitly commit to maintaining a package system.
Even MAAMAN (was FAANG) app stores have been exploited.
FYI your second link is broken or dead.
Re:Podman Desktop v1.5 with Compose onboarding and enhanced ...
by znpy on Friday November 03, 2023 @07:13PM
(#38136288)
This is so true… also different users on the same machine can have their own podman daemon mimicking their own private docker daemon.
In some cases it can be useful to run different containers as different users.
Cheers, but his is not true.
Running a container without root privilege is a security advantage for users who run containers that (inevitably) contain vulnerabilities.