3 ms·
> So, we've made it pretty clear from the start that we're working on ways to make image distribution more secure, but are not claiming that it's more secure ye
by Alupis 12y ago
> So, we've made it pretty clear from the start that we're working on ways to make image distribution more secure, but are not claiming that it's more secure yet
That very clearly makes Docker not secure from it's inception through today currently. That was/is the point of the article.
> but are not claiming that it's more secure yet.
What does "more secure" mean... it's either not secure or is secure.
> This pipeline is performant but completely insecure. Untrusted input should not be processed before verifying its signature. Unfortunately Docker processes images three times before checksum verification is supposed to occur.
> However, despite Docker’s claims, image checksums are never actually checked.
Things like this are by design and at the core of how Docker does what it does. Docker clearly was not built with security considerations in mind.
> Docker exacerbates this situation by running xz as root. This means that if there is a single vulnerability in xz, a call to docker pull could result in the complete compromise of your entire system.
The security implications go on and on.
- mattmcknight 12y agoIt doesn't make Docker "not secure", it means that you need to verify image files in the way you verify other files you download. These changes are irrelevant to the security of Docker itself, for the way I use it with my own images. "it's either not secure or is secure." Security is always a matter of degree.
- Alupis 12y ago> it means that you need to verify image files in the way you verify other files you download That is difficult to script automation that handles all cases. They have mechanisms built in that claim they provide the security you would expect, except that this article exposes their claims are absurdly false and actually dangerous because most users are not going to take the time to verify what the code is actually doing -- ie. they will just trust Docker's claim and move forward, potentially blindly exposing themselves. > Security is always a matter of degree. I agree, except in this case Docker has totally cast most considerations of security out the window. Simple "best practices" like verify user/untrusted input before you begin to work with it are completely ignored as evidenced in this article. > Docker users should be aware that the code responsible for downloading images is shockingly insecure. The issue is Docker sweeps this under the rug and continues to claim their platform is secure. Users trust this, and leave themselves exposed. > It doesn't make Docker "not secure" It sure seems to indicate that Docker is certainly not secure.
- jaegerpicker 12y agoMore secure means exactly what he says. Nothing is ever secure unless it's unplugged from the network. Security is a series of doors between your data and the attackers, making something more secure is simply adding more doors in front of it.
- Alupis 12y ago> I assumed this referenced Docker’s heavily promoted image signing system and didn’t investigate further at the time. Later, while researching the cryptographic digest system that Docker tries to secure images with, I had the opportunity to explore further. What I found was a total systemic failure of all logic related to image security. The issue is Docker has never taken security seriously. From inception up to today. Security is an afterthought, very clearly evidenced by shykes comments above, and by the code being committed. Security for such a core piece of infrastructure, something Docker Inc hopes to thrust into all servers and devices someday, should rightfully be the first and foremost thoughts and part of the initial design of new features. Instead things are designed and developed, and security slips to the side. It takes articles like this to actually motivate Docker to do anything about it.