> I'm using ssh 1.2.27 and am experiencing a new problem that just cropped
> up.  Less than a week ago (and for a month or so before that) I had no
> trouble connecting to all of the boxes on my network.  Suddenly, and
> somewhat intermittently, ssh dies with a "Command terminated on signal 1"
> upon *successful* connection (whether it be via .shosts or entered
> password).  A failed connection results in a "Permission denied," as
> expected.
> 
> I've searched the FAQs and mailing list archive and can't find any
> answers.  I don't believe I have changed any client or daemon
> configuration options.  The really weird part is that I can ssh out of my
> internal network, and then ssh back in to my intended internal target with
> no problems.  It seems to be an incompatibility with my machine.
> 
> All boxes are running the same version of both the client and the server,
> 1.2.27.  The problem occurs between a RedHat 6.0 box and three Solaris
> boxes, running Solaris 2.7, 2.6, and 2.5.  The external machine I can

redhat:~# stty
speed 0 baud; line = 0;
-brkint
redhat:~# ssh solaris
Command terminated on signal 1.
redhat:~# stty 19200
redhat:~# stty
speed 19200 baud; line = 0;
-brkint
redhat:~# ssh solaris
solaris:~#

Some operating systems do not allow terminal speed set to zero. Once set to
something arbitrary (19200 is a sure bet) everything is working just fine.

--
Geir Johannessen          #  [EMAIL PROTECTED]
E B Schieldropsvei 35-25  #  http://2180058000/~joge/
N-7033 TRONDHEIM, NORWAY  #  Tlf private +47-73888989, job +47-73598048
"In case of doubt, make it sound convincing."

Reply via email to