Red Hat Bugzilla – Bug 219026
Portmap and rpc.statd started by default
Last modified: 2007-11-30 17:11:51 EST
Description of problem:
Both portmap and rpc.statd are started by default and listen to the network for
connections. Starting unnecessary network services by default doesn't seem to
fit with the "secure by default" methodology.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC6
Portmap and rpc.statd running and listening for network connections after boot.
Network services should only be started after the user enables them (either
explicitly or by a dependent service being enabled).
These are needed by the NFS client to mount remote filesystem... and
I really don't thing we want the kernel or mount command start them...
So I would like to close this as NOTABUG...
The /etc/rc.d/init.d/netfs init script appears to automagically start portmap if
necessary anyway. (Although clearly this only helps if you're using the netfs
init script to mount your remote file systems).
Well, you can also mount NFS filesystem by hand... and if
portmapper and nfslock was not running, those would
Ok, I'm happy to accept this is not really - closing the bug.