Hi All, I compiled the 3.2.3p1 source on SCO OpenServer 5.0.6. When a client connects to it now, they get stair-stepping everywhere. Issuing an stty sane resolves the issue for that login. For bug 245 in 3.2.2p1, the call to setsid() is sshd.c was bypassed due to problems it was causing with Solaris. However, by allowing this method to be called, the stair-stepping goes away. Thanks, Greg Jewell
Did this happen under 3.1? - Ben On Thu, 23 May 2002, Greg Jewell wrote:> Hi All, > > I compiled the 3.2.3p1 source on SCO OpenServer 5.0.6. When a client connects to it now, they get stair-stepping everywhere. Issuing an stty sane resolves the issue for that login. > > For bug 245 in 3.2.2p1, the call to setsid() is sshd.c was bypassed due to problems it was causing with Solaris. However, by allowing this method to be called, the stair-stepping goes > away. > > > Thanks, > Greg Jewell > > > _______________________________________________ > openssh-unix-dev at mindrot.org mailing list > http://www.mindrot.org/mailman/listinfo/openssh-unix-dev >
--On Thursday, May 23, 2002 12:17 PM -0600 Greg Jewell <greg17 at jewell.net> wrote:> For bug 245 in 3.2.2p1, the call to setsid() is sshd.c was bypassed due > to problems it was causing with Solaris. However, by allowing this > method to be called, the stair-stepping goes away.Sadly, my APUE has gone walkabout, but I think he issue lies in calling setsid() and not opening a terminal. From Solaris termio(7d): The first terminal file opened by the ses- sion leader that is not already associated with a session becomes the controlling terminal for that session. The con- trolling terminal plays a special role in handling quit and interrupt signals, as discussed below. The controlling ter- minal is inherited by a child process during a fork(2). A process can break this association by changing its session using setsid() (see getsid(2)). If OpenSSH is going to call setsid(), it must then open whatever terminal is going to be used (and then dup the fd to 0,1,2). Of course, this probably won't fix the real problem for OpenServer, which seems to be in the propogation of tty settings. -- Carson
On Sat, May 25, 2002 at 02:20:35PM -0400, Carson Gaspar wrote:> If OpenSSH is going to call setsid(), it must then open whatever terminal > is going to be used (and then dup the fd to 0,1,2).setsid() also interacts with setlogin() so OpenSSH is calling setsid() for pty-less sessions for more then 2 years. -m
On Thu, 23 May 2002, Greg Jewell wrote:> Hi All, > > I compiled the 3.2.3p1 source on SCO OpenServer 5.0.6. When a client > connects to it now, they get stair-stepping everywhere. Issuing an stty > sane resolves the issue for that login.I can not duplicate that problem here on my SCO 5.0.6 box. What client are you using?> > For bug 245 in 3.2.2p1, the call to setsid() is sshd.c was bypassed due > to problems it was causing with Solaris. However, by allowing this > method to be called, the stair-stepping goes away.The setsid() call seemed to make no difference here on SCO.> > > Thanks, > Greg Jewell > > > _______________________________________________ > openssh-unix-dev at mindrot.org mailing list > http://www.mindrot.org/mailman/listinfo/openssh-unix-dev >-- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net