"SSH <command>" from .COM - FATAL: ssh_io_register_fd: fd 3 already registered!

[Steven Schweda]

Preliminaries:

alp $ type %sh_test.com

ALP$DKA0:[SMS]RSH_TEST.COM;1

$ rsh alp "show default"

ALP$DKA0:[SMS]SSH_TEST.COM;1

$ ssh alp "show default"

alp $ tcpip show vers

HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 4
on a AlphaStation 200 4/233 running OpenVMS V7.3-1

Fun:

alp $ @ RSH_TEST.COM
ALP$DKA0:[SMS]

alp $ @ SSH_TEST.COM
FATAL: ssh_io_register_fd: fd 3 already registered!

%TCPIP-F-SSH_FATAL, non-specific fatal error condition

Interactively, it's better, but sub-ideal:

alp $ ssh alp "show default"
Authentication successful.

ALP$DKA0:[SMS]
[Hangs here until a key-press, then...]
alp $

Any good reason for this stuff to act this way?

Any good reason that JavaScript is required to submit a message here?

[Karl Rohwedder]

SSH.COM:
$ assign/user sys$command sys$input
$ ssh alp "sh def"

seems to work for me, but the 'wait for a key to be pressed ' happens here also.

mfg Kalle

[Bojan Nemec]

Karl,

This will work, but only when you run this from a terminal. Try $ SUBMIT SSH.COM and you will receive the same error. This is, because ssh expects a terminal as SYS$INPUT,... The same is when you use ssh in a PIPE command. Try:
$ PIPE WRITE SYS$OUTPUT "show default" | SSH ALP
Same error.

So the ssh command is interactive only, and you can not use it in noninteractive command procedures.

Bojan

[Martin Vorlaender]

It's getting stranger still:

Working from the manual, I tried

$ ssh localhost "show system"

and that one does not wait for a key...

BTW: Process Software's SSH implementation doesn't show this behaviour.

cu,
Martin

[Steven Schweda]

> So the ssh command is interactive only, and you can not use it in
> noninteractive command procedures.

Well, duh! Perhaps that's because it's
broken. On a Solaris system, for example:

ung% uname -a
SunOS ung 5.9 Generic_112233-11 sun4u sparc SUNW,Ultra-1

ung% ssh -V
SSH Version Sun_SSH_1.0, protocol versions 1.5/2.0.

ung% find . -name '*_test.sh' -print -exec cat {} \; -exec echo '' \;
./rsh_test.sh
#!/bin/sh
rsh ung 'pwd'

./ssh_test.sh
#!/bin/sh
ssh ung 'pwd'

ung% ./rsh_test.sh
/usr/users/sms

ung% ./ssh_test.sh
/usr/users/sms

No hangs, no problems, just expected output.

For a really good time, try:
ssh_keygen -e key_file_name

I got:

alp $ ssh_keygen -e SMS_ppt_ID_DSA_1024_A
Passphrase needed for key "1024-bit dsa, sms@alp.antinode.org, Fri Jun 27 2003 0
Passphrase :

Do you want to edit key "1024-bit dsa, sms@alp.antinode.org, Fri Jun 27 2003 03:
57:52"
Key unedited and unsaved.lling tty. Cannot read confirmation.

After a SET HOST /LOG, I managed to
unmangle the overwritten text:

You have no controlling tty. Cannot read confirmation.
Key unedited and unsaved.

Now and then a would have helped. I'm
tempted to ask what I need to do to obtain
a "controlling tty", but I'll refrain. For
the morbidly curious:

alp $ ssh_keygen "-V"
alp$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh-keygen2.exe version 2.4.1, compiled Nov 9 2004.

Tell me that this is all better in TCPIP
V5.5. (Is anyone testing this stuff?)

[Jeffery D. Urmann]

Hey Steve,

I see that you are still on OpenVMS v7.3-1. To use TCP/IP Services V5.5, you must upgrade to OpenVMS v8.2 first; at least that`s what the release notes say.

Enjoy,

--Jeff
ex-Zycadian

[Steven Schweda]

Urmann-san:

If the hfa-mn.org e-mail address I (Google)
found is no good, send me a better one.

I'm just a lowly hobbyist. It's only
through the kindness of a stranger that I have
even V5.4. Are you loaning out fresh CD-ROMs
to friendly peons? (I provide pick-up and
return service.)

Also, I suppose it's fair to note that the
release notes (SYS$HELP:TCPIP054.RELEASE_NOTES)
mention one of these problems:

After you execute an SSH remote command, you might need
to press the key to get back to the DCL prompt.

I feel much happier now, knowing this.

sms@antinode-org