Teodor Georgiev wrote:
yes, there are a lot of exploits for RPC's.Well, as much as I'd like to do that, in many cases it's not worth the trouble and resources. So, my next question is, how to properly use hosts.access/hosts.deny to limit who/what can access any of the rpc daemons running on my servers. I have machines sitting across four different subnets, all talking to one another through one service or another (NIS, NFS, MySQL, Mail, SSH, FTP, just to mention a few) and quite honestly, the last time I tried using tcp_wrappers, I ended up breaking just about everything there was to break. Back to the books I guess.
This is 1000000% an intrusion attempt.
Catch the bas*ard :)
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
