[Bug 1273] Interactive mode detection should not be predicated on pty allocation

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Fri May 18 11:25:30 EST 2007


http://bugzilla.mindrot.org/show_bug.cgi?id=1273





--- Comment #4 from John Caruso <jcaruso at arenasolutions.com>  2007-05-18 11:25:27 ---
Maybe I'm not being clear.  I'm not saying that "Connection to <host>
closed" is redundant if it's caused by user interaction.  I'm saying
that I always took "Connection closed" to mean: you started a session
that involved a variable number of commands, and now that session is
done.  But in the code as it stands now "Connection closed" actually
means: you had a tty, and now you're done.  I don't think it's that
useful for SSH to tell you that you had a tty, but I do think it's
useful for SSH to tell you that your variable-length session is now
finished.

The ssh -T (with no remote command) example really illustrates the
difference.  It definitely seems to me that it should print the
"Connection closed" message, but the current code won't do that.  And
that's part of the bug that's not helped by the ssh -q/LogLevel
workaround--in fact there's no way to get the "Connection closed"
message with ssh -T, whether you're doing a truly interactive session,
vi, passwd, sudo -s, or anything else.

Note that I'm NOT just trying to get rid of the "Connection closed"
message...in fact I'm specifically saying I think it should occur in
one context where it currently doesn't, in addition to not occurring in
one context where it currently does.

Anyway, I'm ok with WONTFIX even though I do think this is a bug.  I
just wanted to explain it a bit more since it doesn't seem like my
meaning was getting through.


-- 
Configure bugmail: http://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.


More information about the openssh-bugs mailing list