News for hackers. Stuff that matters.
Re:Introducing Docker Secrets Management by diogomonicapt on Thursday February 09, 2017 @01:43PM (#13609599)
We explicitly chose not to support secrets as ENV variables, since they are prone to being leaked (child processes inhering parent's env; easy to leak ps -e; bug reports usually include ENV of the application; core dumps include ENV of the application, etc etc)
Re:Introducing Docker Secrets Management by tlrobinson on Thursday February 09, 2017 @03:55PM (#13610874)
Makes sense, but how do child processes not have access to the secrets files?
Re:Introducing Docker Secrets Management by diogomonicapt on Thursday February 09, 2017 @11:33PM (#13613249)
My unstated assumption was that when calling something like imagetragick you would be doing the appropriate privilege dropping using setuid and setgid. This is obviously not necessarily the case, but it's at least a lot more common than people cleaning up the ENV before creating a child process.
Re:Introducing Docker Secrets Management by paulddraper on Thursday February 09, 2017 @04:24PM (#13611130)
They do. That point is less valid.