Doctor John wrote:
> FWIW the reason for the file's size was a bunch of dictionary attacks on
> ssh. They failed but why was port 22 open to the internet in the first
> place?

That's what it's for. :-) I mean, really, if you want to get in from 
outside, you leave port 22 open, yes?

Now, if they didn't want anyone to ever get into it from outside the 
LAN, sure. But you didn't say that. ;-)

I'm pretty sure I've seen code to temporarily close port 22 after a 
sufficient number of ssh login failures. Sort of like locking out the 
whole demon, and not just one account.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message