On Mon, 2007-10-22 at 22:34 +0200, [EMAIL PROTECTED] wrote:
Hi,
Oct 22 20:36:13 nms sshd[90657]: Failed password for invalid user gopher
from 77.46.152.2 port 55120 ssh2
user/password authentication for SSH? one way of cleaning up your
logs and killing this type of attack is to
On 10/22/07, Anders B Jansson [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Hi,
Oct 22 20:36:13 nms sshd[90657]: Failed password for invalid user gopher
from 77.46.152.2 port 55120 ssh2
user/password authentication for SSH? one way of cleaning up your
logs and killing this type
@lists.grok.org.uk
Subject: [Full-disclosure] Distributed SSH username/password brute
forceattack
Hello,
since this night I experience distributed SSH username/password
guessing brute force attacks. Anyone seen something similar?
Up until this night always one host tried to guess username
Nothing special, change ssh port.
- Original Message -
From: Philipp [EMAIL PROTECTED]
To: full-disclosure@lists.grok.org.uk
Sent: Monday, October 22, 2007 2:36 PM
Subject: [Full-disclosure] Distributed SSH username/password brute
forceattack
Hello,
since this night I experience
-disclosure] Distributed SSH username/password brute
forceattack
Hello,
since this night I experience distributed SSH username/password
guessing brute force attacks. Anyone seen something similar?
Up until this night always one host tried to guess username/password
combinations until
Hi,
Oct 22 20:36:13 nms sshd[90657]: Failed password for invalid user gopher
from 77.46.152.2 port 55120 ssh2
user/password authentication for SSH? one way of cleaning up your
logs and killing this type of attack is to reconfigure your OpenSSH
to only allow key based logins. stopped my 10M+
[EMAIL PROTECTED] wrote:
Hi,
Oct 22 20:36:13 nms sshd[90657]: Failed password for invalid user gopher
from 77.46.152.2 port 55120 ssh2
user/password authentication for SSH? one way of cleaning up your
logs and killing this type of attack is to reconfigure your OpenSSH
to only allow key
