[Info-vax] SSH

[VAXman- at SendSpamHere.ORG]

In article <RvOdnaR1qrkdDvzQnZ2dnUVZ_jqdnZ2d at giganews.com>, "Richard B. Gilbert" <rgilbert88 at comcast.net> writes:
>On 2/20/2011 9:00 AM, VAXman- @SendSpamHere.ORG wrote:
>> In article<ijofn4$i75$1 at online.de>, helbig at astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) writes:
>>> In article
>>> <df8d248a-64d2-42c2-97ea-fd74dedda748 at w9g2000prg.googlegroups.com>, Neil
>>> Rieck<n.rieck at sympatico.ca>  writes:
>>>
>>>> 2) SSH is based upon port 22. If the source computer can't connect to
>>>> the destination computer on port 22 (lets say it was due to a
>>>> misconfigured firewall or proxy-server) then other technologies like
>>>> SFTP and SCP have no chance of working.
>>>
>>> So SSH, SFTP and SCP all go to port 22 by default?
>>
>>
>> Yes.  They're all manifestations of ssh.
>>
>> You can easily change the port with:
>>
>> $ ssh -p ####
>> $ sftp -oPort=####>
>> $ scp -P ####
>>
>>
>> Don't you just love that unix command line uniformity? ;)
>>
>>
>
>No, but if you must play with Unix, you must either live with the shell 
>as is or modify it to suit your preferences.  I suspect learning the 
>strange language and syntax is easier than rolling your own.  Some 
>people even like it that way.
>
>There are millions of Unix users out there who seem to find the syntax 
>and semantic usable and useful.  They couldn't care less what we think! 
>  ISTR that someone wrote a "DCL shell" but I don't think it ever became 
>popular.

DCL shell or not will make no difference.  unix command switches are parsed
in the utility, not by the shell a la DCL.  My comment was WRT the different
syntax within the 'ssh' suite of commands: ssh, sftp, and scp.  Little 'p',
big 'P' and 'oPort'.
-- 
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.