cm0002@lemmy.world to Programmer Humor@programming.dev · 1 month agoHow Docker was bornlemmy.mlimagemessage-square14fedilinkarrow-up13cross-posted to: programmerhumor@lemmy.ml
arrow-up13imageHow Docker was bornlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 month agomessage-square14fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareDrasla@lemmy.studiolinkfedilinkarrow-up0·1 month agoYou mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
minus-squarekitnaht@lemmy.worldlinkfedilinkarrow-up1·1 month agoSupply chain attack has a definition. And it has nothing to do with DDoS.
minus-squareroofuskit@lemmy.worldlinkfedilinkEnglisharrow-up0·1 month agoThey worry about someone replacing the docker image on the hosting server with a malicious modified version for people to pull down during updates.
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up1·1 month agoThis worry exists for literally every 3rd party dependency, not just docker, and is addressed the same way - by running tests and vulnerability scans in a sandboxed test environment before shipping to prod
You mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
Supply chain attack has a definition. And it has nothing to do with DDoS.
They worry about someone replacing the docker image on the hosting server with a malicious modified version for people to pull down during updates.
This worry exists for literally every 3rd party dependency, not just docker, and is addressed the same way - by running tests and vulnerability scans in a sandboxed test environment before shipping to prod