[Bug 2565] New: High baud rate gets sent, solaris closes pty
bugzilla-daemon at bugzilla.mindrot.org
bugzilla-daemon at bugzilla.mindrot.org
Mon Apr 18 12:49:12 AEST 2016
https://bugzilla.mindrot.org/show_bug.cgi?id=2565
Bug ID: 2565
Summary: High baud rate gets sent, solaris closes pty
Product: Portable OpenSSH
Version: 7.1p2
Hardware: Sparc
OS: Solaris
Status: NEW
Severity: minor
Priority: P5
Component: sshd
Assignee: unassigned-bugs at mindrot.org
Reporter: thogard at abnormal.com
It seems that trying to set the tty baud rate in Solaris to reasonable
modern values is broken resulting in the pseudo tty output being
closed. This effects Solaris 11.3 back to at least Sol 9.
I can replicate it from OS X:
stty ospeed 57600
ssh solaris
Password: ....
(no output)
I can force it 9600 to fix the problem with code that verifies the
problem and fixes it:
case TTY_OP_ISPEED_PROTO2 (and TTY_OP_OSPEED_PROTO2)
...
baud = packet_get_int();
+debug("ibaud=%d",baud);
+baud=9600;
On some clients (such as QNX) stty can be used as a work around. "stty
ispeed 9600;stty ospeed 9600;ssh broken-host" will work.
Is it appropriate to try to fix this in sshd? If so, then should the
proper way to fix this be something along the line of if ( baud >
MAX_BAUD) baud=MAX_BAUD;?
I can't see a way of setting MAX_BAUD other than an config option hack
with a list for broken systems. Even very old Solaris has B57600 in
termios.h so that can't be used as an indicator.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the openssh-bugs
mailing list