Description of problem:
After a recent upgrade I am no longer able to log in to the embedded devices like HP ProCurve ethernet switches or APC master switches - the remote device just closes the connection after receiving the password.
Version-Release number of selected component (if applicable):
openssh-server-5.1p1-2.fc9.i386
openssh-clients-5.1p1-2.fc9.i386
openssh-askpass-5.1p1-2.fc9.i386
openssh-5.1p1-2.fc9.i386
How reproducible:
100 %
Steps to Reproduce:
1. install the above version of openssh
2. try to log in to the remote device using password
Actual results:
connection is closed by the remote side. APC master switches do not
say anything, with HP ProCurve ssh says the following:
Received disconnect from XXX: 2: protocol error: rcvd type 80
Expected results:
Command-line prompt on HP ProCurve (tested 2650, 2848, 4300), menu screen on
APC (tested version 7920).
Additional info:
Downgrading to 5.0p1-1.fc9 fixes the problem. The problem happens at least on i386 and x86_64.
I will attach the two ssh -v sessions (one with 5.0p1-1.fc9, the other one with 5.1p1-2.fc9).
Description of problem:
After a recent upgrade I am no longer able to log in to the embedded devices like HP ProCurve ethernet switches or APC master switches - the remote device just closes the connection after receiving the password.
Version-Release number of selected component (if applicable): server- 5.1p1-2. fc9.i386 clients- 5.1p1-2. fc9.i386 askpass- 5.1p1-2. fc9.i386 5.1p1-2. fc9.i386
openssh-
openssh-
openssh-
openssh-
How reproducible:
100 %
Steps to Reproduce:
1. install the above version of openssh
2. try to log in to the remote device using password
Actual results:
connection is closed by the remote side. APC master switches do not
say anything, with HP ProCurve ssh says the following:
Received disconnect from XXX: 2: protocol error: rcvd type 80
Expected results:
Command-line prompt on HP ProCurve (tested 2650, 2848, 4300), menu screen on
APC (tested version 7920).
Additional info:
Downgrading to 5.0p1-1.fc9 fixes the problem. The problem happens at least on i386 and x86_64.
I will attach the two ssh -v sessions (one with 5.0p1-1.fc9, the other one with 5.1p1-2.fc9).