people?
rgds
Frank
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Charlie Bebber
Sent: Thursday, 17 January 2002 9:13 AM
To: [EMAIL PROTECTED]
Subject: Re: [expert] SSH message not to panic
Mike Leone said:
Meanwhile, that IP belongs
On Thu, 17 Jan 2002, Steve wrote:
I have a Solaris server at work running SSH-2.0-2.0.13 and lately I've
noticed weird addresses in the logs attempting to connect to the sshd
server. It seems that we have similar problems. Here are a few
examples of the log entries:
Dec 27 18:55:10
Charlie Bebber wrote:
Mike Leone said:
Meanwhile, that IP belongs to www.picantecorp.com. A Leader in Email
Enhancement Products and Services.
Why would they want to SSH scan you? You work for them? Are a customer?
Collect the same baseball cards as the webmaster? What?
Yeah, I looked
it and it works well...
portsentry has done this since ver 1 or before. (it worked on Mandrake7.2)
rgds
Frank
-Original Message-
From: Michael Viron [mailto:[EMAIL PROTECTED]]
Sent: Friday, 18 January 2002 12:04 AM
To: [EMAIL PROTECTED]
Subject: RE: [expert] SSH message not to panic
On Wed, 16 Jan 2002, Charlie Bebber wrote:
This isn't the first time I've seen this message in my log and I was just
wondering if anyone on the list might know what the hell it is (if it's
anything other than them looking to see what version of SSH I'm running):
---
Jan 16 10:53:17 oscar
Jan 16 10:53:17 oscar sshd[27848]: scanned from 207.211.22.19 with
SSH-1.0-SSH_Version_Mapper. Don't panic.
---
Be paranoid. Be very paranoid.
Meanwhile, that IP belongs to www.picantecorp.com. A Leader in Email
Enhancement Products and Services.
Why would they want to SSH scan you? You
Mike Leone said:
Meanwhile, that IP belongs to www.picantecorp.com. A Leader in Email
Enhancement Products and Services.
Why would they want to SSH scan you? You work for them? Are a customer?
Collect the same baseball cards as the webmaster? What?
Yeah, I looked that info up too and I
I have a Solaris server at work running SSH-2.0-2.0.13 and lately I've
noticed weird addresses in the logs attempting to connect to the sshd
server. It seems that we have similar problems. Here are a few
examples of the log entries:
Dec 27 18:55:10 sshd2: refused connect from