Operating System - OpenVMS
1829551 Members
3050 Online
109992 Solutions
New Discussion

Re: SSH never resets login fails

 
Edwin Gersbach_2
Valued Contributor

SSH never resets login fails

We encounter the fact that when someone tries to login with a wrong password using SSH, the image TCPIP$SSH_SSHD2.EXE running under the account TCPIP$SSH counts a login failure for the user. However, upon a successfull login, the failure count does not get reset.

As we have several users which only log in using SSH, their counter just goes up.

Is this a known bug?

This is with VMS V7.3-1 (with all current patches) and TCPIP V5.4-ECO1

Edwin
6 REPLIES 6
Willem Grooters
Honored Contributor

Re: SSH never resets login fails

Did you install the lasetst SSH software? There _are_ some issues - at least, there were in that past. It might be that this is one of them.

It's also a possibility that this is a feature of SSH - which is in origin (and current behaviour) a Unix application. So I wouldn't be too surprised if this is a relict of the Unix implementation.

Willem
Willem Grooters
OpenVMS Developer & System Manager
Wim Van den Wyngaert
Honored Contributor

Re: SSH never resets login fails

Just tried the same action with rlogin of tcp 5.3. The reset isn't done either.

Wim
Wim
Wim Van den Wyngaert
Honored Contributor

Re: SSH never resets login fails

Telnet however does clear it. And LAT too.

Wim
Wim
Ian Miller.
Honored Contributor

Re: SSH never resets login fails

TCPIP V5.4-ECO2 is now available with lots of updates for SSH so it may help however I did not see anything corresponding to your problem in the release notes.
____________________
Purely Personal Opinion
Edwin Gersbach_2
Valued Contributor

Re: SSH never resets login fails

Thanks for all the information. I will wait for TCPIP ECO2 to get installed (not my decision) and check again. If the problem persists I will see what a escalation through the official channels reveals.
Edwin Gersbach_2
Valued Contributor

Re: SSH never resets login fails

I missed to close this thread.

Meanwhile we are on ECO5 and the problem is still there. We will soon upgrade to V5.5-ECO1 but I doubt that it will change anything. We are going to escalate through the official channels.

Edwin