Bug#594880: rpcbind loopback test is too strict

2013-07-29 Thread Christoph Anton Mitterer
On Sun, 2013-07-28 at 20:36 -0400, Buck Huppmann wrote: > depends what reserved is defined as, but if it's 1024, then it's > untrusted as well. per rresvport(3): ?? CAP_NET_BIND_SERVICE Bind a socket to Internet domain privileged ports (port numbers less than

Bug#594880: rpcbind loopback test is too strict

2013-07-28 Thread Christoph Anton Mitterer
Because any normal user can bind to ports > reserved? So I don't think it's too strict... therefore can we close the bug? But one thing perhaps,.. shouldn't the test be for <= reserved instead of just < ? Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature

Bug#594880: rpcbind loopback test is too strict

2010-08-30 Thread John Hughes
Package: rpcbind Version: 0.2.0-4.1 Severity: important rpcbind in "secure" mode only allows calls from the loopback address. The check for this is "addr == loopback && port < reserved". This is too strict, why the restriction on the port? -- System Information: Debian Release: squeeze/sid A