Re:Docker is vulnerable to a symlink-race attack
by jetpks on Tuesday May 28, 2019 @06:51PM
(#20035191)
The vulnerability is solved pretty easily by doing your ownership checks _after_ you've opened (but not served) the file. At least, that's how I did it [1]. Despite our pleas and submitted patches, Apache wasn't interested in fixing it upstream.
Re:Docker is vulnerable to a symlink-race attack
by cyphar on Tuesday May 28, 2019 @07:23PM
(#20035414)
Small correction -- you'd want to O_PATH, then verify, and then do a real open (by doing a re-open through /proc/self/fd). Sometimes, tricking you into opening a file is sufficient to cause problems.
Re:Docker is vulnerable to a symlink-race attack
by xrisk on Tuesday May 28, 2019 @01:09PM
(#20032072)
Caddy is brilliant. Configuration is so simple and easy compared to Apache / Nginx.
Re:Docker is vulnerable to a symlink-race attack
by mholt on Tuesday May 28, 2019 @02:30PM
(#20032930)
Thank you!! These comments made my day. Feel free to open an issue on GitHub if you have any ideas for how to improve it even more, since the sky's the limit for Caddy 2.
Re:Docker is vulnerable to a symlink-race attack
by tdhz77 on Tuesday May 28, 2019 @01:21PM
(#20032189)
Have you tried Traefik ?
Re:Docker is vulnerable to a symlink-race attack
by cargoshipit on Tuesday May 28, 2019 @01:27PM
(#20032291)
Are you serious? Their kubernetes setup guide is longer than War and Peace
Re:Docker is vulnerable to a symlink-race attack
by tdhz77 on Wednesday May 29, 2019 @11:37AM
(#20041412)
Not sure what that has to do with anything.
Re:Docker is vulnerable to a symlink-race attack
by tepidandroid on Tuesday May 28, 2019 @01:26PM
(#20032276)
Different use-cases.
Anyway I switched to Caddy [2] even though I deeply love Apache and it has an amazing history behind it.
[1] https://twitter.com/hanno
[2] https://caddyserver.com/