Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: "Milton" <milton.baar@xxxxxxxxx>
- Date: 20 Nov 2006 14:43:01 -0800
Hello Steven
Thanks for your assistance - I don't use my real name as I am a little
shy - and I get plenty of spam already.....following is a more detailed
dump for you - but the dns names have been sanitised with the exception
of the name of the server - which is beta (I have another which is
alpha)....
$ ssh -v beta
debug: Ssh2/SSH2.C:1847: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is
V7.3-2-0
0
debug: SshAppCommon/SSHAPPCOMMON.C:307: Allocating global SshRegex
context.
debug: SshConfig/SSHCONFIG.C:3285: Metaconfig parsing stopped at line
3.
debug: SshConfig/SSHCONFIG.C:842: Setting variable 'VerboseMode' to
'FALSE'.
debug: SshConfig/SSHCONFIG.C:3193: Unable to open ssh2/ssh2_config
debug: Connecting to beta, port 22... (SOCKS not used)
debug: Ssh2/SSH2.C:2813: Entering event loop.
debug: Ssh2Client/SSHCLIENT.C:1607: Creating transport protocol.
debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "publickey" to
usable methods.
debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added
"keyboard-interactive" to
usable methods.
debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "password" to
usable methods.
debug: Ssh2Client/SSHCLIENT.C:1648: Creating userauth protocol.
debug: client supports 3 auth methods:
'publickey,keyboard-interactive,password'
debug: SshUnixTcp/SSHUNIXTCP.C:1356: using local hostname beta.xxx.com
debug: Ssh2Common/SSHCOMMON.C:545: local ip = 192.168.100.201, local
port = 4915
2
debug: Ssh2Common/SSHCOMMON.C:547: remote ip = 192.168.100.201, remote
port = 22
debug: SshConnection/SSHCONN.C:2277: Wrapping...
debug: SshReadLine/SSHREADLINE.C:3651: Initializing ReadLine...
debug: Ssh2Common/SSHCOMMON.C:184: DISCONNECT received: Connection
closed by remote host.
debug: SshReadLine/SSHREADLINE.C:3717: Uninitializing ReadLine...
warning: Authentication failed.
debug: Ssh2/SSH2.C:316: locally_generated = TRUE
Disconnected; connection lost (Connection closed by remote host.).
debug: Ssh2Client/SSHCLIENT.C:1683: Destroying client.
debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki != NULL,
user_pki = NU
LL)
debug: SshConnection/SSHCONN.C:2329: Destroying SshConn object.
debug: Ssh2Client/SSHCLIENT.C:1751: Destroying client completed.
debug: SshAuthMethodClient/SSHAUTHMETHODC.C:104: Destroying
authentication metho
d array.
debug: SshAppCommon/SSHAPPCOMMON.C:320: Freeing global SshRegex
context.
debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki = NULL,
user_pki = NUL
L)
So, as you can see, I am trying to make an ssh connection with the
client on the same node as the server. I have also tried using various
windows-based ssh clients and get the same result. I thought that if
it can't work locally, its not going to work remotely either!
Have rebooted the server, cleaned directories, tried running from a
windows client to the alpha etc....
Cheers
Steven M. Schweda wrote:
From: Gremlin <not.here@xxxxxxxx>
People with names tend to get more help than those with none.
2. [SYSMGR] > ssh -v
[...]
"ssh -v host_name" would tell us more. The messages from a _bare_
"ssh -v" command are not very useful.
3. Again, don't know - I was hoping that (according to my readin of the
manual), it would find that I had no public key and therefore prompt for
a password. It doesn't, I just get...
warning: Authentication failed.
Disconnected; connection lost (Connection closed by remote host.).
So, I am not authenticating but neither am I being prompted for a
password - and this is doing an ssh on the alpha where the ssh server is
installed.
It might help to know what your local host and remote host are. In
my (limited) experience, this stuff behaves approximately as documented.
That is, I've gotten the password prompt(s) when other authentication
methods fail.
The keys are created in the system area, I copied the server's public
key to a [.hostkeys] subdir in my sys$login, protection is s:rewd,
o:rwed, g:re, w:r
The [.hostkeys] directory should be [.ssh2.hostkeys] under SYS$LOGIN,
and the SSH software should hanlde that one on its own. And the
typical protection of the files therein is "(RWD,RWD,,)", and there is a
non-obvious naming convention for them ("KEY_22_SHELL_VISI_COM.PUB", for
example, for "shell.visi.com"), so it's probably best not to fiddle
around in there.
Um, well no - from the prompt I do ssh nodename and I get the connection
refused message. No password prompt, no nothing.
And what is at "nodename", and what, exactly, is the message? A
"connection refused message" normally means that there's no server at
the other end. Other messages normally mean other things. Actual
messages generally mean more than vague descriptions of actual messages.
Things which might help:
0. Cleaning out any spurious [.hostkeys] directories.
1. Descriptions of the two systems, local and remote. (So far, I
know that one of them is a VMS system, which is not enough.)
2. A transcript of an "ssh -v remote_host" session.
------------------------------------------------------------------------
Steven M. Schweda sms@antinode-org
382 South Warwick Street (+1) 651-699-9818
Saint Paul MN 55105-2547
.
- References:
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: Steven M. Schweda
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Prev by Date: Re: Question: Can anyone write device drivers/
- Next by Date: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Previous by thread: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Next by thread: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Index(es):
Relevant Pages
|
