hang on exit bug under Linux

[Michael]

> On Thu, Dec 13, 2001 at 06:56:49PM -0800, Michael wrote:
> > > On Fri, Dec 14, 2001 at 01:58:42AM +0100, Peter Stuge wrote:
> > > > Now off to code up this patch.  Or at least I'll try, had a look at some of
> > > > the code yesterday too but didn't get anywhere..
> > > 
> > > Cool.
> > > 
> > > You need options processing code (readconf.c) and session-exit
> > > processing code. When the client gets a session-exit message, and
> > > that was the last session still "alive", then do as the user wanted.
> > > The things to do could be many, as I've suggested before and as I'll
> > > repeat:
> 
> [...]
> 
> > The behavior may be different for V1 vs V2
> > 
> > The old V1 behavior simply exits unconditionally -- whereas V2 waits 
> > and presumably would be altered by the proposed modification
> > or....
> > are V1 and V2 to operate in the same manner???
> 
> SSHv1 and SSHv2 are radically different in this area. The v1
> behaviour cannot be modified. But with v2, the client makes the
> decision of when to quit, either by letting the user make the
> decision (~.) or by knowing ahead of time what the user would have
> the client do (hang, background, ~., SIGHUP).
> 
> So this would clearly be a SSHv2-only option.
> 
> Correct me if I'm wrong.
> 
> Cheers,

I happen to agree, but when an old v1 client connects to openssh, the 
"new behavior" prevails. That's one thing that would have to be 
fixed.
Michael at Insulin-Pumpers.org