Re: Look what I've found
From: erik (erik_at_geenspam.vanwesten.net)
Date: 09/12/03
- Next message: TechLead1: "How to authenticate a user/password in C"
- Previous message: Chris Cox: "Re: dsniff questions"
- In reply to: Nico Kadel-Garcia: "Re: Look what I've found"
- Next in thread: Nico Kadel-Garcia: "Re: Look what I've found"
- Reply: Nico Kadel-Garcia: "Re: Look what I've found"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 12 Sep 2003 20:24:26 +0200
Nico Kadel-Garcia wrote:
> Silviu Minut wrote:
>> I just found the following entry in my /var/log/secure:
>>
>> Sep 11 19:20:56 zeus sshd[14580]: Did not receive identification
>> string from 193.95.229.34
>>
>> So I finger -l root@193.95.229.34 - he's there.
>> I also http://193.95.229.34 and there's some toolkits! So the guy is
>> up to something. I'm not sure what created that entry in my logs.
>> Remotely, I did
>>
>> telnet my.ip.add.ress 22
>>
>> and the entry created was
>>
>> Sep 11 23:14:44 zeus sshd[14829]: Bad protocol version identification
>> '????^F' from 35.9.26.229
>>
>> and I also scanned myself (also remotely) with nmap and I got no log.
>> Runing RH9.0 with latest patches, iptables, with everything closed,
>> except port 22.
>>
>> Has he broken in already? How can I tell?
>> Should I send email to root@193.95.229.34?
>> Do I call the police? The FBI? KGB? :)
>>
>> Actually, I don't think he broke in. It was kind of fun to see all
>> that, so I though I'd share it with others.
>
> Looks like that site is in Austria: the KGB would probably be more
> competent than growsing to the FBI, since it doesn't actually involve
> money yet, but send them a note anyway.
Bad advice. Please study some geography first.
> And the materials look like a
> typical idiot script-kiddie, not competent enough to be *REALLY*
> dangerous. He was probably port-scanning for active ports on your and
> other boxes, found SSH, gathered the init string for it, then
> disconnected. The "sshscan" tool does the same thing when scanning a
> subnet for the SSH versions: some of the older ones do have some known
> exploits.
And what is wrong with just ringing the doorbell. There certainly is no
law against that. You cannot even call it portscanning. Testing one
port isn't considered portscanning.
>
> And go to his upstream host:
> http://www.samspade.org/t/lookat?a=193.95.229.34 shows that his
> upstream is apparently "uta.at", who get their connectivity from
> ip-plus.net. They're more likely to act than that site is.
Why would they want to act. Please do not overreact.
EJ
-- Remove the obvious part (including the dot) for my email address. http://www.vanwesten.net for examples of ipf and pf.
- Next message: TechLead1: "How to authenticate a user/password in C"
- Previous message: Chris Cox: "Re: dsniff questions"
- In reply to: Nico Kadel-Garcia: "Re: Look what I've found"
- Next in thread: Nico Kadel-Garcia: "Re: Look what I've found"
- Reply: Nico Kadel-Garcia: "Re: Look what I've found"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|