cm0002@lemmy.world to Programmer Humor@programming.dev · 3 months agoHow Docker was bornlemmy.mlimagemessage-square34fedilinkarrow-up1827arrow-down125cross-posted to: [email protected]
arrow-up1802arrow-down1imageHow Docker was bornlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 3 months agomessage-square34fedilinkcross-posted to: [email protected]
minus-squareDrasla@lemmy.studiolinkfedilinkarrow-up1·2 months agoYou mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
minus-squarekitnaht@lemmy.worldlinkfedilinkarrow-up6arrow-down3·2 months agoSupply chain attack has a definition. And it has nothing to do with DDoS.
minus-squareroofuskit@lemmy.worldlinkfedilinkEnglisharrow-up2·2 months 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-up9·2 months 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·2 months agoI was just answering a question. I had the same response above.
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up2·2 months agoAnd I was just adding extra details
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.
deleted by creator
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