search for: timeoutp

...ConnectionAttempts https://bugzilla.mindrot.org/show_bug.cgi?id=2918 --- sshconnect.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/sshconnect.c b/sshconnect.c index 4862da5e..b837a83a 100644 --- a/sshconnect.c +++ b/sshconnect.c @@ -454,11 +454,12 @@ waitrfd(int fd, int *timeoutp) { struct pollfd pfd; struct timeval t_start; - int oerrno, r; + int oerrno, r, next_timeout; monotime_tv(&t_start); pfd.fd = fd; pfd.events = POLLIN; + next_timeout = *timeoutp; for (; *timeoutp >= 0;) { r = poll(&pfd, 1, *timeoutp); oerrno = errno; @@ -473,6 +474,7...

On Sat, Jan 7, 2017 at 2:30 PM, Peter Moody <mindrot at hda3.com> wrote: > so I spent a bit of time looking at this and it seems like the only > way to go, at least if I want to keep it in ssh_connect_direct(), is > to use pthreads. further, it seems like getting that accepted is > something of a long shot: Sorry, pthreads is a non-starter. I would have thought that using

...fixed delay for how long to wait before + * starting the next connection attempt [...] recommended value for a + * default delay is 250 milliseconds. + */ +#define CONNECTION_ATTEMPT_DELAY 250 + static int -timeout_connect(int sockfd, const struct sockaddr *serv_addr, - socklen_t addrlen, int *timeoutp) +ssh_connect_timeout(struct timeval *tv, int timeout_ms) { - int optval = 0; - socklen_t optlen = sizeof(optval); + if (timeout_ms <= 0) + return 0; + ms_subtract_diff(tv, &timeout_ms); + return timeout_ms <= 0; +} - /* No timeout: just do a blocking connect() */ - if (*timeoutp <...

....com,A.B.C.D") at ../ssh-keyscan.c:615 #8 0x00007ffff7f86f65 in main (argc=6, argv=0x7fffffffe778) at ../ssh-keyscan.c:781 For what it's worth, as far as the arguments to that select() call are concerned... (gdb) p state->connection_in $1 = 213 (gdb) p timeoutp $2 = (struct timeval *) 0x0 (I'll leave the session up in case you'd like me to poke around any further.) This is running on an RHEL 6.6 machine, should the network stack be called into question... -- You are receiving this mail because: You are watching the assignee of the bug. You...

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