cm0002@lemmy.world to Programmer Humor@programming.dev · 7 days agoHow Docker was bornlemmy.mlimagemessage-square34fedilinkarrow-up1815arrow-down123
arrow-up1792arrow-down1imageHow Docker was bornlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 7 days agomessage-square34fedilink
minus-squareDrasla@lemmy.studiolinkfedilinkarrow-up1·7 days agoYou mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
minus-squareroofuskit@lemmy.worldlinkfedilinkEnglisharrow-up2·7 days 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-up8·7 days 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
minus-squareroofuskit@lemmy.worldlinkfedilinkEnglisharrow-up2·7 days agoI was just answering a question. I had the same response above.
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up2·7 days agoAnd I was just adding extra details
minus-squarekitnaht@lemmy.worldlinkfedilinkarrow-up5arrow-down3·7 days agoSupply chain attack has a definition. And it has nothing to do with DDoS.
You mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
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
I was just answering a question. I had the same response above.
And I was just adding extra details
Supply chain attack has a definition. And it has nothing to do with DDoS.
deleted by creator