bug in SSH?

[Phillip Helbig---remove CLOTHES to reply]

SSH Secure Shell OpenVMS (V5.5) 3.2.0

TCPIP 5.4 ECO 5

VMS 7.3-2

When logging in via SSH, as opposed to telnet, I see the line

@DISK$:[DIR]ANNOUNCE.TXT

printed on the screen, instead of the contents of
DISK$:[DIR]ANNOUNCE.TXT itself. Is this a bug in SSH?

[Peter 'EPLAN' LANGSTOeGER]

In article <f2gvp0$e1g$1...@online.de>, hel...@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:
>SSH Secure Shell OpenVMS (V5.5) 3.2.0
>
>TCPIP 5.4 ECO 5
>
>VMS 7.3-2

VMS V8.3 with TCPIP V5.6 is current. But you know this and it also makes no
difference (SSH-2.0-3.2.0 SSH Secure Shell OpenVMS V5.6 VMS_sftp_version 2).

>When logging in via SSH, as opposed to telnet, I see the line
>
> @DISK$:[DIR]ANNOUNCE.TXT
>
>printed on the screen, instead of the contents of
>DISK$:[DIR]ANNOUNCE.TXT itself. Is this a bug in SSH?

Yup. A bug (or a missing feature or whatever you like to call it) since day 1.
You also don't get a welcome message, neither SYS$WELCOME nor the default msg.
(btw. TCPware SSH does it different/better, there you get the announcement,
and yes, the content, between the username and the password prompt, and
after successfull authentication you get the SYS$WELCOME like in plain VMS)

And it is not the only bug. TCPIP SSH still lacks a lot of VMS specialities
(like not requiring /NETWORK for login or being able to run SHUTDOWN.COM and
a documented/supported method of not allowing SCP/SFTP with SSH also, ...)
cause of the common source pool with the (already murdered) Tru64.

--
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail pe...@langstoeger.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

[Ian Miller]

no its a feature :-)

To get a message displayed on login you need to specify the file to be
displayed in the ssh config

[Chuck Aaron]

There's a memory leak as well with SFTP. HP Engineering has it to work on.

[daryl...@att.net]

On May 17, 12:21 am, hel...@astro.multiCLOTHESvax.de (Phillip Helbig---

Phillip,

Source:
http://h71000.www7.hp.com/DOC/83final/tcprn/TCPIP_V56_REL_NOTES.PDF

3.12.8 SSH Messages
This section includes notes and restrictions pertaining to SSH session
messages.
· Normally, the translation of the system logical name SYS$ANNOUNCE
is displayed after authentication is complete. In this version of SSH,
no
automated mechanism exists for displaying this text as a prelogin
banner.
To provide a prelogin banner from a text file, create the file
SSH_BANNER_MESSAGE. containing the text to be displayed before login.
To enter multiple lines in the banner text, make sure each line ends
with an
explicit carriage-return character except the last line.
Save the banner message file in the
TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2] directory, with privileges that
allow it to be read by the user account [TCPIP$SSH].

If you do not use the default file name and location for the message
banner file, define them using the BannerMessageFile option in the
TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG. file. Specify
the location and file name of your banner message file as the argument
to the
option using one of the following formats:
BannerMessageFile TCPIP$SSH_DEVICE:[TCPIP$SSH]BANNER1.TXT
BannerMessageFile /TCPIP$SSH_DEVICE/TCPIP$SSH/BANNER2.TXT
BannerMessageFile /etc/banner3.txt
Note that the argument may be in either OpenVMS or UNIX format and is
not case sensitive. (If multiple definitions for the same option are
included in
the configuration file, the last one listed will take effect.)

I hope this helps.
Daryl Jones