[CentOS] Access Threshhold by IP -- WAS: Crashing Nameservers
Bryan J. Smith
thebs413 at earthlink.netTue Jan 3 22:29:08 UTC 2006
- Previous message: [CentOS] Access Threshhold by IP -- WAS: Crashing Nameservers
- Next message: [CentOS] Cheap PC's anyone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kai Schaetzl <maillists at conactive.com> wrote: > How should portsentry help in this case? > It makes only sense to use it for ports that aren't bound > to a service. Excuse me? That's just _1_ of portsentry's various capabilities. Portsentry _can_ bind itself to a port being service by another program. > Or are you talking of a newer "portsentry" I don't know of? > (AFAIK development of the sentry family was discontinued > years ago.) I don't deny that the Sentry Tools (currently 1.2 on SourceForge) are getting aged. But portsentry is still a nice tool for quickly blacklisting IPs after several failed login attempts. -- Bryan J. Smith Professional, Technical Annoyance b.j.smith at ieee.org http://thebs413.blogspot.com ---------------------------------------------------- *** Speed doesn't kill, difference in speed does ***
- Previous message: [CentOS] Access Threshhold by IP -- WAS: Crashing Nameservers
- Next message: [CentOS] Cheap PC's anyone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list