[Info-vax] SSH on VAX - performance impact of break in attempts

[Bob Koehler]

In article <30bb3a36-2c46-4041-bf98-2f2d0329ffa7 at x21g2000yqa.googlegroups.com>, urbancamo <mark at wickensonline.co.uk> writes:
> 
> I have attempted a number of strategies to reduce this impact:
> 
> 1. I have defined an AllowUsers list so only named users are allowed.
> 2. I have set AuthInteractiveFailureTimeout to 30 so that there is a
> 30 second delay between login attempts from the same host/session.
> 3. I have set RequiredAuthentications to publickey,password so that
> both a password and a valid public key are required.

   I didn't see what stack you're using, but I think all of them
   allow you to limit the number of concurrent connections.  If you can
   set it to just above the number of people who normally log in, then
   many of the attacks will bounce off without using up so much CPU.

   Of course, during the attack, real users would hit the same limit.