2 ms·
If the best you can say for the current defaults is that they're easy to change, then it's probably time to change the defaults. The article doesn't just say t
by foldr 4y ago
If the best you can say for the current defaults is that they're easy to change, then it's probably time to change the defaults.
The article doesn't just say that dropping privileges is a 'pain', but points out that a security model based on binding a port as root (or another specially privileged user) and then dropping privileges has been a persistent source of security issues. The article links to several detailed explanations of this (e.g. https://wibblement.blogspot.com/2021/11/the-persistent-idiocy-of-privileged.html https://wibblement.blogspot.com/2021/11/the-persistent-idioc..., https://www.staldal.nu/tech/2007/10/31/why-can-only-root-listen-to-ports-below-1024/ https://www.staldal.nu/tech/2007/10/31/why-can-only-root-lis...).
The one-line configuration change also doesn't work well if the service is executed via an interpreter or VM. Authbind also has its edge cases: https://www.reddit.com/r/golang/comments/cqlpnq/comment/ewyluyh/ https://www.reddit.com/r/golang/comments/cqlpnq/comment/ewyl...