search for: stdout_buff

...writing to the application) After applying the following patch, everything started to work for me: *** clientloop-old.c Wed Oct 17 22:05:30 2001 --- clientloop.c Wed Oct 17 22:01:46 2001 *************** *** 937,947 **** } /* Output any buffered data for stdout. */ while (buffer_len(&stdout_buffer) > 0) { len = write(fileno(stdout), buffer_ptr(&stdout_buffer), buffer_len(&stdout_buffer)); ! if (len <= 0) { ! error("Write failed flushing stdout buffer."); ! break; } buffer_consume(&stdout_buffer, len); stdout_bytes += len; --- 937,...

...====================================================== RCS file: /cvs/src/usr.bin/ssh/clientloop.c,v retrieving revision 1.21 diff -u -r1.21 clientloop.c --- clientloop.c 2000/04/19 07:05:48 1.21 +++ clientloop.c 2000/04/26 01:54:54 @@ -873,6 +873,8 @@ len = write(fileno(stdout), buffer_ptr(&stdout_buffer), buffer_len(&stdout_buffer)); if (len <= 0) { + if (errno == EGAIN) + continue; error("Write failed flushing stdout buffer."); break; } @@ -884,6 +886,8 @@ len = write(fileno(stderr), buffer_ptr(&stderr_buffer), buffer_len(&stderr_buff...

...if (len < 0 && (errno == EINTR || errno == EAGAIN)) { +294 /* do nothing */ +295 } else if (len <= 0) { +296 fdout_eof = 1; +297 } else { +298 buffer_append(&stdout_buffer, buf, len); +299 fdout_bytes += len; +300 } +301 } +302 /* Read and buffer any available stderr data from the program. */ +303 if (!fderr_eof && FD_ISSET(fderr, readset)) { +304 len =...

...1 server_loop and the v2 server_loop2, the v1 loop appears to have significantly more checks for breaking the loop: if (((fdout_eof && fderr_eof) || (child_terminated && child_has_selected)) && !packet_have_data_to_write() && (buffer_len(&stdout_buffer) == 0) && (buffer_len(&stderr_buffer) == 0)) { if (!channel_still_open()) break; as well as other useful logging information, like: debug("End of interactive session; stdin %ld, stdout (read %ld, sent %ld), stderr %ld bytes.",...

...if (len < 0 && (errno == EINTR || errno == EAGAIN)) { +308 /* do nothing */ +309 } else if (len <= 0) { +310 fdout_eof = 1; +311 } else { +312 buffer_append(&stdout_buffer, buf, len); +313 fdout_bytes += len; +314 } Line # 309 needs to be changed to ... +309 } else if (len < 0) { Making the above change in the 2.3.0p1 and the 2.5.1p1 source distributions solves the problem, however, I don...

...< 0 && (errno == EINTR || errno == EAGAIN)) { /* do nothing */ } else if (len <= 0) { - fdout_eof = 1; + verbose ("read from fdout returns zero?"); + if (child_terminated) + fdout_eof = 1; + else + fdout_maybe_eof = 1; } else { buffer_append(&stdout_buffer, buf, len); But no doubt it would be much better if somebody who understands how ptys work in Solaris 7 could figure out the *right* way to fix this. I don't recommend adding that hack to the code. With the old Yl?nen ssh 1.2.26, the behaviour is a bit different: A Control-C to bash's p...

...nism. */ channel_prepare_select(readsetp, writesetp, maxfdp, nallocp, rekeying); if (!compat20) { - /* Read from the connection, unless our buffers are full. */ + /* Read from the connection, unless our buffers are full. */ if (buffer_len(&stdout_buffer) < buffer_high && buffer_len(&stderr_buffer) < buffer_high && channel_not_very_much_buffered_data()) @@ -342,13 +378,7 @@ if (buffer_len(&stderr_buffer) > 0) FD_SET(fileno(stderr), *wr...

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,

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

http://bugzilla.mindrot.org/show_bug.cgi?id=124 ------- Additional Comments From markus at openbsd.org 2002-02-23 06:10 ------- what does "streaming" mean? what does "output reports" mean? do you have more detailed reports? do you have debugging output? what clients are involved? what servers? does the same happen with openssh 3.0.2? does the same happen with a recent