When using the ConnectTimeout option, socket remains non-blocking after connecting, which may (?) cause trouble.
Created attachment 527 [details] Patch (for non-portable version) patch not tested, but it is rather short and should work ok.
I'll take care of this. You are correct. The impact is minor though - we will just spin and waste CPU while waiting for the peer's identification.
similar fix applied - thanks
Mass change of RESOLVED bugs to CLOSED