[Info-vax] stumped by SSH

[Jan-Erik Soderholm]

Den 2016-02-07 kl. 12:11, skrev Simon Clubley:
> On 2016-02-07, Phillip Helbig (undress to reply) <helbig at asclothestro.multivax.de> wrote:
>> In article <n95hh0$a1r$1 at news.albasani.net>, Jan-Erik Soderholm
>> <jan-erik.soderholm at telia.com> writes:
>>
>>>> Local: VMS cluster.  Remote: Linux.
>>>
>>> I think that Simon implied that:
>>>
>>> "Local" is where you are trying to start a SSH session *from*.
>>> That is, the envoronment where you are when issuing the SSH command.
>>> Or in other words, the "SSH client".
>>>
>>> "Remote" is where you are trying to connect *to*.
>>> Where the "SSH server" is running.
>>>
>>> If we do not agree on that, this will be realy weird... :-)
>>
>> Sorry for the confusion.  My VMS box is local, but the problem is
>> connecting to it from outside.  So, geographically, VMS is local and
>> Linux is remote.  The client is on the Linux side and the server on the
>> VMS side.
>>
>
> So VMS is the SSH server.
>
> [Jan-Erik is right; normally, when one talks about a "remote" system,
> the default implication in this type of discussion is _that_ system is
> the server and hence is the one being accessed, as a server, from a
> local client. That's what I assumed as well.]
>

Right, there is a geographical local/remote and there is a technical
local/remote... :-)

In most cases client=local and server=remote.

But you can of course also have a client that is remote
and a server that is local, which seem to be the case
in this thread... :-)

(And no, I will not add X client/Server here... :-) )

That is why it is important to be very clear on what
one is talking about.


In a guide to SSH that I happend to have (seems to be
from the V5.6 timeframe) it says:

 > To get detailed tracing information, on the OpenVMS
 > SSH server, enter the following command:
 >
 > $ ASSIGN/SYS "-i -d 6" TCPIP$SSH_SERVER_PARAM
 >
 > Trace information is written to the
 > TCPIP$SSH_HOME:TCPIP$SSH_RUN.LOG file.



Jan-Erik.


> Some questions:
>
> Are all accounts (both successful and unsuccessful) being accessed from
> the same remote Linux box ?
>
> Have you _actually_ done a $ show int after a login failure ?
>
> What's the final status in the accounting log for the login attempt ?
>
> For an account which you cannot log into from a Linux client, can you
> login to the VMS server from a _VMS_ SSH client on another box ?
>
> To turn on debugging in the Linux SSH client, use "ssh -v" on your
> Linux command line. Increase the number of v's above (as in "ssh -vv"
> or "ssh -vvv") to gradually increase the amount of debugging information.
>
> If that doesn't reveal anything obvious, try the same for a successful
> login attempt and see where things start to differ.
>
> Simon.
>