Date: Sat, 15 Mar 1997 11:36:25 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: ywliu@phi.Sinica.EDU.tw (Yen-Wei Liu) Cc: question@freebsd.org, hackers@freebsd.org Subject: Re: SSH-1.2.17 & FreeBSD 2.1.7 strange problem Message-ID: <199703151836.LAA04518@phaeton.artisoft.com> In-Reply-To: <9703151001.AA12889@phi.Sinica.EDU.tw> from "Yen-Wei Liu" at Mar 15, 97 06:01:16 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> Sorry I send this message to two lists, which I am not on. However, I think > experienced programmers may be interested and helpful. > > I have one Sun SparcStation running SunOS 5.5, one PC running FreeBSD > 2.1.6 and one 2.1.7, and the other Linux 2.0.x. All of them were all > installed Secure Shell (SSH) 1.2.17 and happily connected with one > another. > > After I updated one 2.1.6 to the current 2.1.7, a strange thing happened. > This 2.1.7 can connect to 2.1.6 and Linux (in shell interactive mode), but > cannot connect to SunOS 5.5 ! Everytime it sends out a message "Command > terminated on signal 1" and then disconnects the request from 2.1.7, while > 2.1.6 can connect to this SunOS 5.5 in shell mode !! After more than > 4 hours fighting with this problem, I guess it's more related to FreeBSD > , rather than to Ssh. The two PCs differs only in OS version : 2.1.6 and > 2.1.7 , and 2.1.6 is OK but not for 2.1.7 !! The shell is getting a signal 1 (SIGHUP), probably because "carrier" is dropped on the PTY, probably because of an authorization failure. You will need to provide better debugging information (see the ssh source site for information). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703151836.LAA04518>