News for hackers. Stuff that matters.
Re:Linux Namespaces and Go Don't Mix by brandon on Friday June 02, 2017 @02:16PM (#14472143)
There's a simple-ish workaround for the privileged port issue if you can't just use CAP_NET_ADMIN: http://play.golang.org/p/dXBizm4xl3

The namespace issues are unfortunately a lot tougher to address.

Re:Linux Namespaces and Go Don't Mix by vbernat on Friday June 02, 2017 @02:38PM (#14472323)
It's only reliable if none of your dependencies are spawning goroutines during initialization. If this is the case, some goroutines (yours' or the dependencies') can end up with increased privileges.
Re:Linux Namespaces and Go Don't Mix by brandon on Friday June 02, 2017 @10:38PM (#14474700)
The workaround functions by opening the privileged socket and re-executing the binary as an unprivileged user with access to the filehandle. Any background goroutines would exit with the privileged parent.

Also: please don't spawn goroutines during init(). There's generally a better time and place, and in the event that you justifiably need a package-level background routine you can spawn it on demand with a sync.Once.

Re:Linux Namespaces and Go Don't Mix by the8472 on Saturday June 03, 2017 @01:39AM (#14475169)
But you also want drop that privilege after using it to get the same effect as the "daemonize dance" GP referred to. And that's also per-thread, just like namespaces.