Date: Wed, 4 Jan 2006 15:44:00 -0500 From: Vivek Khera <vivek@khera.org> To: stable@FreeBSD.org Subject: Re: rpcbind lingering on IP no longer specified on command line Message-ID: <D0C52AF2-A5A9-42BF-8CD8-CFC01235D92C@khera.org> In-Reply-To: <43BC24E7.6090800@FreeBSD.org> References: <A97CE7DE-1841-41D0-B702-E82761FCDD3B@khera.org> <43BC24E7.6090800@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Jan 4, 2006, at 2:41 PM, Doug Barton wrote: > What does 'sockstat | grep rpcbind' tell you? # sockstat | grep rpcbind root rpcbind 11382 5 stream /var/run/rpcbind.sock root rpcbind 11382 6 dgram -> /var/run/logpriv root rpcbind 11382 7 udp4 127.0.0.1:111 *:* root rpcbind 11382 8 udp4 192.168.100.200:111 *:* root rpcbind 11382 9 udp4 *:664 *:* root rpcbind 11382 10 tcp4 *:111 *:* As Dmitry Morozovsky points out, it seems it always listens to tcp *: 111 which seems to be a bad thing. I'm running 6.0-RELEASE-p1. This came up because of some security scans we're having run for some compliance certificates we need... Can anyone explain why rpcbind will still bind to all tcp interfaces?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D0C52AF2-A5A9-42BF-8CD8-CFC01235D92C>