Users started reporting "DT messaging system could not be started" error when trying to directly log in to a Solaris 8 box via Hummingbird Exceed (X-Windows client on Windows) (Window Mode: Single, Start-up Mode: XDMCP-query).
I found the precise reason why it started happening;
**********
»
216.239.41.104/search?q= ··· 22&hl=enOther suggestions were to check the directory permissions, check the
/etc/net/*/hosts files, delete the files in /var/dt/tmp, and
make sure
rpcbind is running (for ttdbserverd).**********
The problem is I was asked to turn off a bunch of these services, including ttdbserverd, after a recent security audit by an external consulting company that cited RPC portmapper (port 111) as a potential vulnerability. The silly thing is now everything in /etc/inetd.conf with the word RPC is now deemed vulnerable. My question is: Is rpcbind/ttdbserverd (default Solaris 8 version) really a security concern? How best to work around the error while placating the RPC-paranoia?