search for: client_alive_schedul

http://bugzilla.mindrot.org/show_bug.cgi?id=52 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |1274 nThis| | ------- You are receiving this mail because: ------- You are the assignee for

...idletime_last=0; /* The last time something happened + * for idletimeout. */ /* * This SIGCHLD kludge is used to detect when the child exits. The server * will exit after that, as soon as forwarded connections have terminated. @@ -193,7 +194,9 @@ struct timeval tv, *tvp; int ret; int client_alive_scheduled = 0; - + /* Secs until idletimeout, zero if no idletimeout */ + int max_time_seconds=0; + /* * if using client_alive, set the max timeout accordingly, * and indicate that this particular timeout was for client @@ -208,6 +211,24 @@ } else client_alive_scheduled = 0; + + i...

...--- openssh-2.9p2.orig/serverloop.c Sat Apr 14 02:28:03 2001 +++ openssh-2.9p2/serverloop.c Mon Aug 20 23:33:30 2001 @@ -190,7 +190,6 @@ wait_until_can_do_something(fd_set **readsetp, fd_set **writesetp, int *maxfdp, u_int max_time_milliseconds) { - struct timeval tv, *tvp; int ret; int client_alive_scheduled = 0; @@ -259,25 +258,15 @@ if (max_time_milliseconds == 0 || client_alive_scheduled) max_time_milliseconds = 100; - if (max_time_milliseconds == 0) - tvp = NULL; - else { - tv.tv_sec = max_time_milliseconds / 1000; - tv.tv_usec = 1000 * (max_time_milliseconds % 1000); - tvp = &...

Hi openssh-unix-dev subscribers :) I have found that ServerAliveInterval & ServerAliveCountMax have some bug. Basically the ssh-alive check function (that verify the peer is alive) is called only if no data at all gets into ssh (when it should work only for server channel).I am pretty sure developers know about this ..anyway I have tried to fix this issue. Here is the patch: diff -rNu

...**readsetp, fd_set **writesetp, int *maxfdp, int *nallocp, u_int max_time_milliseconds) { - struct timeval tv, *tvp; + + struct timeval tv, *tvp; + /* SD Mod: added variable steno_timer*/ + static struct timeval steno_timer = {0, 50000}; int ret; int client_alive_scheduled = 0; - - /* + long int prev_timer_val = 0; + /* * if using client_alive, set the max timeout accordingly, * and indicate that this particular timeout was for client * alive by setting the client_alive_scheduled flag. @@ -183,11 +217,11 @@ *...

...Assignee: unassigned-bugs at mindrot.org Reporter: wiwi at progon.net If RekeyLimit is enabled, ClientAlive messages will not be sent, ever! Problem seems to be: serverloop.c: wait_until_can_do_something(...) max_time_milliseconds is set to the remaining time to a rekey. client_alive_scheduled never gets set, as max_time_milliseconds!=0: if (compat20 && max_time_milliseconds == 0 && options.client_alive_interval) { client_alive_scheduled = 1; max_time_milliseconds = (u_int64_t)options.client_alive_interval * 1000; } The if clause might need changed to...

...-1 && buffer_len(&stdin_buffer) > 0) FD_SET(fdin, *writesetp); } + notify_prepare(*readsetp); /* * If we have buffered packet data going to the client, mark that @@ -278,6 +319,8 @@ error("select: %.100s", strerror(errno)); } else if (ret == 0 && client_alive_scheduled) client_alive_check(); + + notify_done(*readsetp); } /* @@ -467,6 +510,8 @@ connection_in = packet_get_connection_in(); connection_out = packet_get_connection_out(); + notify_setup(); + previous_stdout_buffer_bytes = 0; /* Set approximate I/O buffer size. */ @@ -572,6 +617,7 @@...

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

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

...2_9_p2_w_gss_krb5_named_keys.10/serverloop.c Thu, 03 May 2001 16:12:13 -0400 jd (OpenSSH/i/16_serverloop 1.1 644) +++ 2_9_p2_w_gss_krb5_named_keys.10(w)/serverloop.c Thu, 25 Oct 2001 15:11:49 -0400 willian (OpenSSH/i/16_serverloop 1.1 644) @@ -259,18 +259,25 @@ if (max_time_milliseconds == 0 || client_alive_scheduled) max_time_milliseconds = 100; + if (!channel_still_open()) + max_time_milliseconds = 1000; + if (max_time_milliseconds == 0) tvp = NULL; else { tv.tv_sec = max_time_milliseconds / 1000; tv.tv_usec = 1000 * (max_time_milliseconds % 1000); tvp = &tv; + debug3("selec...

http://bugzilla.mindrot.org/show_bug.cgi?id=52 ------- Additional Comments From t8m at centrum.cz 2005-02-03 22:06 ------- Created an attachment (id=801) --> (http://bugzilla.mindrot.org/attachment.cgi?id=801&action=view) Patch submitted by John Bowman (bowman at math.ualberta.ca) This patch was attached to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=39128 Also see

Hi, We have upgraded the openssh 4.6P1 on Solaris 8 servers. After upgrade we get the below error message whenever we execute the remote commands using ssh. Please let me know what the fix is for this. Apr 8 03:03:43 dvsrv10 sshd[25379]: [ID 800047 auth.info] Accepted publickey for osteam from 10.0.93.31 port 35856 ssh2 Apr 8 03:03:50 dvsrv10 sshd[25381]: [ID 800047 auth.error] error:

Hi OpenSSH developers, I am using openSSH (now 2.9.9p2, but prob occurs in 2.9p2 also) to execute commands on a remote machine which outputs data to stdout then pipes it to another invocation of ssh which connects back to the first machine in the same way, where it starts a program to read and store the output from the command on the second machine. I am using the "command" option in

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach