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

[VAXman- at SendSpamHere.ORG]

In article <8dofpuFqf7U1 at mid.individual.net>, billg999 at cs.uofs.edu (Bill Gunshannon) writes:
>In article <00AA28DB.0416FD2E at sendspamhere.org>,
>	VAXman-  @SendSpamHere.ORG writes:
>> In article <8dn96lF8lcU2 at mid.individual.net>, billg999 at cs.uofs.edu (Bill Gunshannon) writes:
>>>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!!
>> 
>> But 'ssh' and 'sftp' have optional switches for modifying the port.  If there
>> is a user that is suppsed to get into your system, then they should know the
>> port.
>
>You mean like that customer that I don't even know about yet?

You would have potential customers 'ssh'ing into a system?

This one you"re going to have to illustrate.

-- 
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.