full-disclosure - Re: Any update on SSH brute force attempts?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20041016140536.GA2532@sentinelchicken.org>
From: tim-security at sentinelchicken.org (Tim)
Subject: Re: Any update on SSH brute force attempts?

> And the few present users attempted:
> adm
> apache
> nobody
> operator
> root

In addition to what others have suggested, you could use PAM to enforce
account lockouts in the event that the attacker does focus the attempts
on a real account.  The Linux module for this is pam_tally.  You can
also put an unlock script on a cron job to then prevent DoS of all of
your accounts.  Not perfect, but effective.

hth,
tim