[Info-vax] SSH on VAX - performance impact of break in attempts

[VAXman- at SendSpamHere.ORG]

In article <kk8ik7-7s5.ln1 at Ubuntu.mike-r.com>, Mike Rechtman <mike at rechtman.com> writes:
>On 26/08/10 16:40, Bill Gunshannon wrote:
>> In article<4C75EDE9.5060502 at vsm.com.au>,
>> 	Jeremy Begg<jeremy.removethis at vsm.com.au>  writes:
>>> Hi Mark,
>>>
>>> I can recommend from personal experience both of the following solutions:
>>>
>>> 1.  Change the incoming port to something other than 22.  This almost always
>>> prevents your system being targetted by the bots.  (I typically add another
>>> three digits to the port number.)
>>
>> It also prevents legitimate users from getting in if they don't already
>> know what port you are using.  Reminds me of the guy I know locally who
>> was trying to run a webserver from home even though it is prohibited by
>> his AUP with his ISP.  He said he got around it by not using port 80 and
>> moving the port around a lot.  Seemed rather silly to me as no one would
>> ever know where to find his webserver!!
>>
>> bill
>>
>Also, when SSHing in from an outside site, I often find that non-standard ports 
>(say ports other than 22,23 and 80) are blocked. Possibly illogical, but thats 
>what their particular admin wants.

Blocked by whom?  The site you want to get into?  Or, the network you are using
at the time?

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.