Firewall Wizards mailing list archives
RE: rpc.statd message log
From: "Melson, Paul" <PMelson () sequoianet com>
Date: Thu, 24 Apr 2003 13:51:13 -0400
If it's RedHat 7.2, fully patched, then it should not be vulnerable. If you are using it for port forwarding and you know exactly what ports should be allowed to and from where, consider using iptables to prevent any traffic that you do not specifically wish to allow. This would have prevented an external attacker from connecting to statd even if it were running. PaulM
-----Original Message----- This is a Linux Red Hat 7.2 with all the latest patches working as a port forw box for our schools web server. This really is a low usage machine, compared to you big boys, and I have scanned it with a demo version of Retina. The results were great, as far as I can tell, in terms of open and shut ports. After I closed off the portmap service, the only port open now is 22 for ssl. Since yesterday, I have not seen this message in the logs. Amazing what a little maintenance will do.
_______________________________________________ firewall-wizards mailing list firewall-wizards () honor icsalabs com http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
Current thread:
- rpc.statd message log Robert E. Martin (Apr 24)
- Re: rpc.statd message log Devdas Bhagat (Apr 24)
- Re: rpc.statd message log R. DuFresne (Apr 24)
- <Possible follow-ups>
- RE: rpc.statd message log Melson, Paul (Apr 24)
- Re: rpc.statd message log Robert E. Martin (Apr 25)
- RE: rpc.statd message log Melson, Paul (Apr 25)