Date: Mon, 11 Oct 2021 08:56:22 -0700 From: Chris <bsd-lists@bsdforge.com> To: Yuri <yuri@freebsd.org> Cc: Freebsd hackers list <freebsd-hackers@freebsd.org> Subject: Re: Possible to start the process with setuid while allowing it to listen on privileged ports? Message-ID: <1db5aa695aac2b6a0b5bf4bd3b553af5@bsdforge.com> In-Reply-To: <6e98975c-34e5-246f-5b86-700b5f847815@rawbw.com> References: <6e98975c-34e5-246f-5b86-700b5f847815@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-10-11 08:50, Yuri wrote: > Normal way to do this is for the application to first listen on the port and > then setuid. > > > My question is about the situation when the application isn't willing to do > this. > > > The project author says that setuid is too difficult in Go and Linux allows > to do > this through systemd: > > https://github.com/coredns/coredns/issues/4917#issuecomment-939892548 > > > Can in FreeBSD the process be run as a regular user but still be allowed to > bind > to privileged ports? Doesn't (X)org do this? If I'm right, maybe there's a clue there? HTH --Chris > > > Thanks, > > Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1db5aa695aac2b6a0b5bf4bd3b553af5>