delayed Access Reject response

[A.L.M.Buxey at lboro.ac.uk]

Hi,

> It was set to 1, but the actual delay is clearly bigger than that. In 
> fact, it doesn't seem to be constant, it seems to wait until a new 
> request was sent, and then it unleashes the reject.
> 
> I set reject_delay to 0 and now there's no delay, but I'm not sure I 
> like it that way, due to possible brute-force attacks.

correct. that is why reject_delay exists. and yes, a value of 1
wont directly map to a count of 1 as there is also the
cleanup_delay which occurs.

alan