Attacker damaged my system via ssh. I' m shocked. 1568

Davide Bianchi

Um, yeah, right. If that were really the case, you would not have needed to sip the context at the point you did. You specifically replied to "This is only "security thought obscurity"," Cutting everything AFTER a comma to state "no not really". To me your comment was to challenge what I said. Rather than your current claim of agreeing with what I said.

Perhaps you could be a little more clear with what you said. Your statement "...is only to get rid of all the automatic scripts that only checks port 22 (there are many)" is VASTLY different than what you are claiming now "is only getting rid of the entries in the log". "... getting rid of the entries in the log" does NOTHING to enhance security.

What ever "really attacking" means. Someone "really attacking" is probably going to do the obvious first. Since it looks like the obvious worked here, there was no reason to go for anything more advanced. In otherwords, you have no idea if this was "just a moron trying a generic attack".

Which is, the last I checked still an attack regardless of if YOU want to say "really" or not.

What are your babbling about? Since the attack looks like it was done on port 22, you have no idea if the person doing the attack could have found ssh on a different port and been just as successful. Of course an expert hacker is going to try the obvious first.

-- NOTE: Name change. Was mattleftcoast. Dan C. Gets caught apparently Plagiarizing: Yeah, this it the type critical of me!