> added: MaxAUTHErrors Yay! I just had a bad one, yesterday. It was a very fast one that caused the server to heave under the load. This is a GREAT addition.
Suggestion: that we be able to specify the time within which the max number can occur. This is mainly because the frequency of such attacks (i.e. the time between each name in the dictionary) can vary a lot. Getting some form of stats on this would be nice, too, even if not necessary. It might be useful to know 1) a running overall total number of IPs that try such attacks, 2) average number of complete attacks per IP, and 3) the average time between names tried in any given attack that caused the blocking. These may be too much to include in stats, but, as one who has seen this kind of attack cause serious problems to my server, I'd certainly be interested to know what these guys are doing and how often. Thanks again for this function, even if it remains in its current state. T. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
