News for hackers. Stuff that matters.
Re:Don't expose the docker socket, even to a container by throwaway2048 on Thursday September 24, 2015 @12:53AM (#10269891)
there is no mention of seccomp because virtually no software can utilize it.
Re:Don't expose the docker socket, even to a container by kentonv on Thursday September 24, 2015 @02:01AM (#10270083)
Sandstorm.io (disclosure: my project) applies mandatory seccomp and other attack surface reduction yet manages to run a lot of apps with only minimal modification:

https://docs.sandstorm.io/en/latest/developing/security-prac...

Admittedly, though, "only minimal modification" is probably too much modification for Docker's goals. That's fair. But I don't think that gives them a pass to pretend the problem doesn't exist.

Re:Don't expose the docker socket, even to a container by geofft on Thursday September 24, 2015 @01:09AM (#10269935)
As a Chrome, systemd, and Sandstorm user, I'm a little curious what you mean.
Re:Don't expose the docker socket, even to a container by rwmj on Thursday September 24, 2015 @03:59AM (#10270401)
qemu uses seccomp. If you run your VMs with libvirt, then seccomp can be used to protect the host from qemu easily and routinely.
Re:Don't expose the docker socket, even to a container by simoncion on Thursday September 24, 2015 @06:56AM (#10270903)
OpenSSH and BIND use seccomp. :)