topic Re: SSH and sys$announce in Operating System - OpenVMS

SSH and sys$announce

Piet Timmers_1 — Thu, 26 Jun 2008 06:19:23 GMT

An other SSH question.

When using telnet (or DECnet, LAT etc.) the user gets the sys$announce on his terminal.

Is there a way to get this when using SSH to log in.

Thanks.

Piet

Re: SSH and sys$announce

Heinz W Genhart — Thu, 26 Jun 2008 06:43:32 GMT

Hi Piet

You can define the BannerMessageFile in tcpip$ssh_device:[tcpip$ssh.ssh2]sshd2_config.

For example:
BannerMessageFile /SYS$SYSDEVICE/VMS$COMMON/SYSMGR/ANNOUNCE.TXT

Regards

Geni

Re: SSH and sys$announce

Piet Timmers_1 — Thu, 26 Jun 2008 08:23:51 GMT

Heinz, thanks.

Now I know to search on the internet to the string bannermessagefile.

It works, but this message is displayed after the login prompt, and before the password prompt. This not as it works when using telnet or DECnet login.

Can this configured to get the same behaviour als with telnet logins?

Thanks.

Piet

Re: SSH and sys$announce

Heinz W Genhart — Thu, 26 Jun 2008 08:32:31 GMT

Hi Piet

I do not agree. The banner message appears before the login Prompt.

Here an example:

$ ssh system@gdc00y
******************************************************************************

Unauthorized access is prohibited. Misuse will be prosecuted.

Unberechtigter Zugriff ist verboten. AllfÃ¤lliger Missbrauch wird geahndet.

AccÃ¨s interdit sans autorisation. Tout abus sera puni.

L'accesso senza autorizzazione Ã¨ vietato. Ogni abuso sarÃ punito.
******************************************************************************

IX Admin Server

system's password:

Regards

Geni

Re: SSH and sys$announce

Piet Timmers_1 — Thu, 26 Jun 2008 08:46:01 GMT

In your example this is correct, but we are using a terminal emulator (putty, reflection) to login.

First a question for "login as:" appears, then after entering the user name, the banner message will be displayed.

Greetings,

Piet

Re: SSH and sys$announce

Richard Whalen — Thu, 26 Jun 2008 09:26:27 GMT

The terminal emulator may be suppressing, or delaying the message. Though the SSH2 protocol has provisions for messages both before and after the authorization of the user, not all clients handle the messages in the same way.

Re: SSH and sys$announce

Heinz W Genhart — Thu, 26 Jun 2008 10:47:31 GMT

Hi Piet

We are also using putty. The string

login as:

is coming from putty and at this time putty did not yet connect to the remote node.

But you can define the username which putty is using to connect. See in putty on the left hand side 'Connection', 'Data' and there define the Auto-login username.

After defining the auto-login username it looks like this:

Using username "geni".
******************************************************************************

Unauthorized access is prohibited. Misuse will be prosecuted.

Unberechtigter Zugriff ist verboten. AllfÃ¤lliger Missbrauch wird geahndet.

AccÃ¨s interdit sans autorisation. Tout abus sera puni.

L'accesso senza autorizzazione Ã¨ vietato. Ogni abuso sarÃ punito.
******************************************************************************

Admin Server

geni@gdcw7d's password:

Regards

Geni

Re: SSH and sys$announce

Steven Schweda — Thu, 26 Jun 2008 12:23:56 GMT

I get "SYS$ANNOUNCE" on my system, although
it's not exactly what I'd like. Around here:

alp $ ssh alp
Authentication successful.
@ SYS$MANAGER:ANNOUNCE.TXT

[... other [sy]login.com stuff ...]

I enjoy the lameness of this behavior so much
that I'll be sad if/when it ever gets done
right.

Re: SSH and sys$announce

Piet Timmers_1 — Thu, 26 Jun 2008 12:34:34 GMT

Heinz,

The string "login as:" is comming from putty, and putty has not yet made a conmnection to the host.

When I connect using putty, I see the string "login as:" and a new process tcpip$ss_bg.... om my OpenVMS server.
So putty already has a connection to the host?

Another thing: when I make a connection using putty, I see the "login as:" prompt.
At that moment a new process is created. When I do not answer to this question, how long does it take before that process is being stopped?
On a telnet login, you get "error reading command input" after 20 seconds.
So when I start very many putty sessions, connect to my host, it will be overloaded by tcpip$ss_bg.... processes, and nobody is able to login, without using a username or password, or not?

Greetings,

Piet