[CentOS] Access Threshhold by IP -- WAS: Crashing Nameservers
Kai Schaetzl
maillists at conactive.comTue Jan 3 22:02:49 UTC 2006
- Previous message: [CentOS] 64-bit CentOS 4.2 -- What is x86-64? "Long Mode" memory model ...
- Next message: [CentOS] Access Threshhold by IP -- WAS: Crashing Nameservers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bryan J. Smith wrote on Fri, 30 Dec 2005 22:28:45 -0800 (PST): > Portsentry is how I deal with this for services that are TCP > Wrapper enabled. I believe every vsftpd build I've seen on > every distro is so enabled. How should portsentry help in this case? It makes only sense to use it for ports that aren't bound to a service. Or are you talking of a newer "portsentry" I don't know of? (AFAIK development of the sentry family was discontinued years ago.) Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
- Previous message: [CentOS] 64-bit CentOS 4.2 -- What is x86-64? "Long Mode" memory model ...
- Next message: [CentOS] Access Threshhold by IP -- WAS: Crashing Nameservers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list