similar to: [Bug 207] Connect timeout patch

http://bugzilla.mindrot.org/show_bug.cgi?id=207 ------- Additional Comments From jclonguet at free.fr 2002-05-23 05:02 ------- Created an attachment (id=101) Patch for OpenSSH-3.2.2p1 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=656 Summary: ConnectTimeout option broken Product: Portable OpenSSH Version: 3.7.1p1 Platform: All URL: http://charts.free.fr OS/Version: All Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=207 ------- Additional Comments From jclonguet at free.fr 2002-04-07 06:19 ------- Created an attachment (id=63) ConnectTimeout patch ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=207 Summary: Connect timeout patch Product: Portable OpenSSH Version: 3.1p1 Platform: All URL: http://charts.free.fr/openssh-3.1p1-timeout-1.02.patch OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:

http://bugzilla.mindrot.org/show_bug.cgi?id=207 ------- Additional Comments From jclonguet at free.fr 2002-06-27 06:27 ------- Created an attachment (id=118) Patch for OpenSSH-3.4p1 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=207 ------- Additional Comments From jclonguet at free.fr 2002-10-17 18:36 ------- Created an attachment (id=154) --> (http://bugzilla.mindrot.org/attachment.cgi?id=154&action=view) Patch for OpenSSH-3.5p1 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

http://bugzilla.mindrot.org/show_bug.cgi?id=785 Summary: ssh client socket may have O_NONBLOCK flag set Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy:

This patch avoids spending too much time during connect() when doing an ssh()/scp() on a down host. It uses a new client option called ConnectTimeout and is useful for rsync or rdist commands using ssh(). See http://bugzilla.mindrot.org/show_bug.cgi?id=207 for detailled info. -------------- next part -------------- --- openssh-3.6.1p1/readconf.c.ORIG Tue Apr 15 23:06:30 2003 +++

http://bugzilla.mindrot.org/show_bug.cgi?id=91 ------- Additional Comments From djm at mindrot.org 2003-05-24 11:07 ------- See also bug #207 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Fix and/or document issues raised in this thread: https://www.redhat.com/archives/libguestfs/2017-February/msg00010.html Rich.

If I set a timeout for a specific host's key does it set the timeout for just that key/host? I.e. if I do something like in ~/.ssh/config:- # # # backup, use public-key authentication # Host backup IdentityFile ~/.ssh/backup_id_rsa IdentityAgent 600 Will it just time out the key saved for backup and leave any other keys with the default no timeout? --

Here is the version of this patch for the last portable version of OpenSSH (3.5p1), as it is not included in the main tree. The patch avoids waiting to long when using ssh() or scp() on a down host, it is usefull when you have to update many hosts via rsync or rdist themselves relying upon ssh(). It enables a new option 'ConnectTimeout' to control exactly the timeout value, so that it can

Hi Scott, You've entirely missed my point. Yes, if I connect directly to a host, I can use '-4' to force IPv4. When connecting through a proxy, I can't easily control which address family to use, nor the TCP connect timeout. Sure, if I use netcat to proxy, I could supply a '-4' to it to force connecting over IPv4. But making that permanent is also a pain because I want

Dear openssh developers and users, I'm new to the list, and my apologies if this question has been asked before. I've tried to look for answers and haven't succeeded, which is why I'm asking. Here's the situation: I'm connect to a dual-stacked host with A and AAAA records. The IPv6 connectivity to the host is broken. When connecting to the host directly from my client

Here are the new versions of this widely used patch for OpenSSH 3.2.2p1 and 3.2.3p1. The patch avoids waiting to long when using ssh() or scp() on a down host, it is usefull when you have to update many hosts via rsync or rdist themselves relying upon ssh(). It enables a new option 'ConnectTimeout' to control exactly the timeout value, so that it can be used even on slow links. These

Hello OpenSSH folks, This was a really minor knit, but I noted while I was developing a pexpect module for ssh that setting ConnectTimeout to 0 in the options to ssh sets the login timeout to infinite time. I was wondering whether or not this was a documentation bug and/or potential clarification that could to be made, or if this was a software bug that needs to be fixed. I don't see

Hello, I'm using Ruby's Shellwords module, which generates a string from an array, suitable for shell evaluation. Ruby's implementation prefers escaping whitespace with a backslash rather than quotes. However, this appears to cause some kind of issue in Rsync when it computes argv from -e option. Here is an example command generated by some Ruby code: rsync --archive --stats -e

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

Hi all, I have somewhat a strange problem that I could not figure out, maybe someone here can lelp. I have a script that uses scp to distribute files to many servers, I use '-o BatchMode=yes -o ConnectTimeout=2 options so the scp will not get stuck if something is wrong with the remote host. If the remote host is down (non-pingable) or sshd is down the timeout option works and the scp