Re:Don't expose the docker socket, even to a container
by codemac on Wednesday September 23, 2015 @11:17PM
(#10269638)
Docker is a rootkit over HTTP.
[ Parent
| on HN ]
Re:Don't expose the docker socket, even to a container
by voltagex_ on Thursday September 24, 2015 @12:36AM
(#10269835)
>A rootkit is a collection of computer software, typically malicious, designed to enable access to a computer or areas of its software that would not otherwise be allowed (for example, to an unauthorized user) while at the same time masking its existence or the existence of other software.
Doesn't really describe Docker, does it?
Re:Don't expose the docker socket, even to a container
by codemac on Thursday September 24, 2015 @02:11AM
(#10270111)
It does if you're talking about `docker -d` and --privileged.
Re:Don't expose the docker socket, even to a container
by KirinDave on Thursday September 24, 2015 @02:28AM
(#10270157)
Rootkits hide themselves. Docker makes no effort to do so.
I know you're trying to make joke, but it's not funny.
Re:Don't expose the docker socket, even to a container
by codemac on Thursday September 24, 2015 @03:12PM
(#10273892)
That's the joke, literally.
This is a blog post about how docker is insecure when you can get root perms over a socket the docker daemon exports when you explicitly map it back into a docker container... as if it's unexpected when it's explicitly docker's design and the command line you provided.
Oh well, I did think it was funny.