hang on exit bug under Linux

[Nicolas Williams]

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.


> Michael at bizsystems.com


Correct me if I'm wrong.

Cheers,


Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.