ssh tutorial
gmspro
gmspro at yahoo.com
Sun Jun 7 00:14:20 UTC 2009
Yes,I am not ssh administrator.
> Chris' explanation is good.
>
> May I suggest the original questioner needs to "find" the
> information
> needed to connect to "that particular" ssh server.
> The original
> questioner may need to talk with the person (ssh server
> administrator)
> who is running the ssh server. The ssh server
> administrator should have
> a cookbook telling how to connect to his server. I am
> assume the
> original questioner is not the ssh server administrator.
>
> The ssh server administrator can configure which ssh
> protocol version(s)
> of ssh will work, what types of authentication will work,
> whether X11
> will will be forwarded, and many other options. The
> ssh server
> administrator can even force a particular user to execute a
> specific
> program when the user tries to connect.
>
> The ssh server administrator will need to create an account
> and make
> configuration changes to allow people to connect to that
> account.
> Sometimes, a ssh server administrator might create an
> "anonymous"
> account that runs a particular program, such as cvs to
> allow people to
> anonymously retrieve source code. In every case that
> I can think of,
> the original questioner will need to find documentation on
> how to
> connect or will need to talk with the ssh server
> administrator.
>
> I would also suggest, using the "-v" option on the ssh
> command.
> I believe one can type ssh -v -v -v user at host
> From "man ssh", "
> -v Verbose mode. Causes ssh to
> print debugging messages about its
> progress. This is helpful
> in debugging connection, authentica-
> tion, and configuration
> problems. Multiple -v options increase
> the verbosity. The
> maximum is 3.
> "
>
> The output from the "-v -v -v" options may help the ssh
> server
> administrator help the original questioner find out what is
> wrong when
> the original questioner tries to connect.
More information about the fedora-list
mailing list