News for hackers. Stuff that matters.
Re:Try PostgreSQL 9.5 by syncerr on Saturday July 04, 2015 @10:33PM (#9832315)
Neat. Just be cautious as docker containers aren't yet secure.

https://docs.docker.com/articles/security/

Re:Try PostgreSQL 9.5 by anonova on Saturday July 04, 2015 @11:44PM (#9832426)
> Docker containers are, by default, quite secure; especially if you take care of running your processes inside the containers as non-privileged users (i.e., non-root).

I'm not quite seeing the sense of insecurity here, especially from the conclusion. Like any piece of software, it's up the user to not use "dangerous" configurations.

Re:Try PostgreSQL 9.5 by marcosdumay on Sunday July 05, 2015 @10:47AM (#9833720)
Linux containers are at most a privilege escalation away from breaking.

Also, isn't Docker people the ones talking about unikernels? Where everything run not only with superuser powers, but at kernel level?

Re:Try PostgreSQL 9.5 by rmgraham on Sunday July 05, 2015 @12:50PM (#9834076)
Though in a Unikernel, the kernel only implements what is needed to run the service. So a database, for example, would be lacking functionality like a shell to escape to.. or even a TTY to run that shell on.. or an implementation of connect() to even initiate outbound TCP connections, in the extreme case.
Re:Try PostgreSQL 9.5 by azernik on Sunday July 05, 2015 @09:08AM (#9833403)
Except that the default is for processes inside containers to run as root.

So, "by default, quite secure; except this one default that exposes you to some very nasty attacks unless you override it".

Re:Try PostgreSQL 9.5 by rmgraham on Saturday July 04, 2015 @10:53PM (#9832343)
Thanks for taking a look, and looking close enough to see that it uses Docker :-)

Was there some specific aspect or attack vector that came to mind? Or did you mean it more as a blanket warning?

Re:Try PostgreSQL 9.5 by syncerr on Saturday July 04, 2015 @11:04PM (#9832362)
Generally. And only because I see other companies doing this sort of thing. I'd like docker to be a solution here, but we're not quite there.