bug in channel_still_open() ?

[Markus Friedl]

On Thu, Apr 05, 2001 at 05:07:24AM -0400, Richard E. Silverman wrote:
> The code appears to assume that normally, the server should end the SSH
> session when there are no open channels remaining.  This only seems
> reasonable if you think about the typical behavior of a standard
> command-line SSH client; I don't think it's correct in general.  There
> need not be any session channel, larval or otherwise.  The OpenSSH client
> always opens a channel which it calls "client-session", even with -N; it
> just never issues an SSH "exec" request on it if -N is given.  But there's
> no protocol requirement for this -- the ssh.com Windows client, when given
> the analogous option ("disable terminal" checkbox), establishes no
> channels at all.

thanks, i changed this in openssh-current. this is very old code

> More generally, I see no reason to assume that a channel count of 0 in the
> connection protocol means that the transport should be closed.  I think a
> client should expect to be able to establish a transport session, start
> the connection protocol, start some channels for whatever purposes, close
> them all, wait an hour, and then start some more channels.

all this is due to a reuse of protocol v1 code, about a year
ago i did not know less about v2 than i know today.

-m