Re: rpcbind security

On Fri, Jun 17, 2022 at 8:42 PM Gustavo Rios wrote: > Excuse me, but how does rpcbind know that a incoming request, for > set/unset, comes from the root user ? > Theo has already told you how the *portmap* program decides that: by looking at the host and port the request is coming from. (There

rpcbind security

Excuse me, but how does rpcbind know that a incoming request, for set/unset, comes from the root user ? Thanks. -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus

Re: rpcbind security

I am certain you can find it yourself. Gustavo Rios wrote: > may some here points me where rpcbind is implemented ? I would like to see > the C code > of it. > Thanks. > > Em sex., 17 de jun. de 2022 às 00:20, Theo de Raadt > escreveu: > > Gustavo Rios wrote: > > > Hi folks! > > > >

Re: rpcbind security

may some here points me where rpcbind is implemented ? I would like to see the C code of it. Thanks. Em sex., 17 de jun. de 2022 às 00:20, Theo de Raadt escreveu: > Gustavo Rios wrote: > > > Hi folks! > > > > How does openbsd rpcbind prevent ordinary users to unset a given rpc port > > mapping

Re: rpcbind security

Gustavo Rios wrote: > Hi folks! > > How does openbsd rpcbind prevent ordinary users to unset a given rpc port > mapping registered by, for instance, the root user ? Poorly. It will only allow local root (who request upon a reserved port) to touch ports which are reserved (< 1024), and 2049 is

rpcbind security

Hi folks! How does openbsd rpcbind prevent ordinary users to unset a given rpc port mapping registered by, for instance, the root user ? Thanks. -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus