connecting to non-responding hosts: 1 hr timeout (fwd)

Markus Friedl markus.friedl at informatik.uni-erlangen.de
Thu May 3 06:51:50 EST 2001


On Tue, May 01, 2001 at 08:37:38PM -0700, Carson Gaspar wrote:
> Sadly, this is _not_ portable, as you seem to imply by your portable url 
> below. I'm one of the people who got async connect working with socks5. 
> When I asked the late Richard Stevens about some edge conditions, his 
> response was "I don't know. Let me know what you find out". Here There Be 
> Dragons. I ended up writing a test case bit of C code, and running it on a 
> bunch of different OSs. It wasn't pretty. The main problem lies in getting 
> the return code from the async connect if it fails. The only portable way 
> is via getsockopt(), and many older systems don't support the SO_ERROR 
> option. What select returns on a failed call is also 
> implementation-specific.

well, then openssh is not portable :)

the current channels.c uses async connects this way.



More information about the openssh-unix-dev mailing list