search for: chan_input_wait_drain

...ct line. It seems (!) to have caused no problems with the previous openssh snapshot version openssh-SNAP-20001016, 2.3.0p1 and the latest snapshot (openssh-SNAP-20001114). The patch adds 3 lines to nchan.c in a switch stmt (line 100). It simply caters for the cases where the input channel state is CHAN_INPUT_WAIT_DRAIN or CHAN_INPUT_CLOSED. In these cases it simply exits (breaks) from the switch stmt. This seems to be necessary now because an earlier fix caused nchan to be called twice when closing a session. The first time is okay, but the second (with the channel now in one of the above states) causes the error...

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

...er, next in the modified version is the call to 'session_free' as seen in the latter server output. In the original version 'session_exit_message' calls 'chan_read_failed' because the input channel state is not (yet) closed (CHAN_INPUT_CLOSED); it is open but gets changed to CHAN_INPUT_WAIT_DRAIN (it seems). As such it attempts to read more info; gets none and goes through the 'read failed'; 'input open -> drain'; 'input open -> closed'; 'send eof' sequence. *Then* 'session_free' is called (as part of session close), and we end up back in sessio...

When I encounter the problem with TCP port forwarding locking up, I'll see this on the client window (if I haven't invoked ssh with -q): chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected This is with Blowfish encryption. I have to kill and restart the client when this happens. Phil

The 4.6p1 sshd is logging this error during remote commands or file transfers: error: channel 0: chan_read_failed for istate 3 Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d. The commands and transfers work correctly, so the error message appears to be spurious. The error message does not appear when processing logins. Otherwise 4.6p1 is running without any apparent problems. This error

I'm reading this fine article on O'Reilly: http://linux.oreillynet.com/lpt/a//linux/2001/11/08/ssh_keystroke.html <quote> The paper concludes that the keystroke timing data observable from today's SSH implementations reveals a dangerously significant amount of information about user terminal sessions--enough to locate typed passwords in the session data stream and reduce the

http://bugzilla.mindrot.org/show_bug.cgi?id=1306 Summary: Spurious : "chan_read_failed for istate 3" errors from sshd Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

...the the following states (in nchan.h) describe the status. #define CHAN_INPUT_OPEN 0x01 So the message was printed when istate was CHAN_INPUT_OPEN and ostate was CHAN_OUTPUT_CLOSED. cf. From nchan.h. /* possible input states */ #define CHAN_INPUT_OPEN 0x01 #define CHAN_INPUT_WAIT_DRAIN 0x02 #define CHAN_INPUT_WAIT_OCLOSE 0x04 #define CHAN_INPUT_CLOSED 0x08 /* possible output states */ #define CHAN_OUTPUT_OPEN 0x10 #define CHAN_OUTPUT_WAIT_DRAIN 0x20 #define CHAN_OUTPUT_WAIT_IEOF 0x40 #define CHAN_OUTPUT_CLOSED...

...ates @@ -137,6 +139,28 @@ } } static void +chan_wont_read_12(Channel *c) +{ + debug("channel %d: wont read", c->self); + switch (c->istate) { + case CHAN_INPUT_OPEN: + debug("channel %d: input open -> drain", c->self); + chan_shutdown_read(c); + c->istate = CHAN_INPUT_WAIT_DRAIN; +#if 0 + if (buffer_len(&c->input) == 0) { + debug("channel %d: input: no drain shortcut", c->self); + chan_ibuf_empty(c); + } +#endif + break; + default: + debug("channel %d: chan_wont_read for istate %d", + c->self, c->istate); + break; + } +} +s...

...} + /* End SD Mod */ packet_send(); buffer_consume(&c->input, len); c->remote_window -= len; } - } else if (c->istate == CHAN_INPUT_WAIT_DRAIN) { + } + /* + * Begin SD Mod: + * packet does not contain data, we are not in a draining + * state and timing manipulation is desired, check if bogus + * count is below threshold. + *...

Hello, In response to the timing analysis attacks presented by Dawn Song et. al. in her paper http://paris.cs.berkeley.edu/~dawnsong/ssh-timing.html we at Silicon Defense developed a patch for openssh to avoid such measures. Timing Analysis Evasion changes were developed by C. Jason Coit and Roel Jonkman of Silicon Defense. These changes cause SSH to send packets unless request not to,

...26 @@ channel_pre_x11_open(Channel *c, fd_set } } +static void +channel_pre_mux_client(Channel *c, fd_set *readset, fd_set *writeset) +{ + if (c->istate == CHAN_INPUT_OPEN && + buffer_check_alloc(&c->input, CHAN_RBUF)) + FD_SET(c->rfd, readset); + if (c->istate == CHAN_INPUT_WAIT_DRAIN) { + /* clear buffer immediately - partial packet */ + buffer_clear(&c->input); + chan_ibuf_empty(c); + } + if (c->ostate == CHAN_OUTPUT_OPEN || + c->ostate == CHAN_OUTPUT_WAIT_DRAIN) { + if (buffer_len(&c->output) > 0) + FD_SET(c->wfd, writeset); + else if (c-&...

http://bass.directhit.com/openssh_snap/ Starting tonight I plan on tracking changes very closely with the OpenBSD tree. I need people to test the latest snapshot (9/14 at of right now) and report success or failure on compiling. I am starting this now because we are looking at a code freeze soon and I really want to ensure it compiles and runs on all existing platforms. So we (the portable