Community
Participate
Working Groups
RC3 I wanted to connect to our repository, which doesn't use the default extssh protocol. As you see from the screenshot, I realized my mistake and cancelled the connection ("Cancel" is disabled in the progress dialog). Nothing happened until the request timed out (see second screenshot). The cancel should be recognized in a timely manner or changed to a disabled "OK" with no option to cancel the operation.
Created attachment 12573 [details] Connection in progress...
Created attachment 12574 [details] Timeout error
For SSH 2, the socket connect code is reponsive (I have verified this with strategic break points). However, the JCraft libraries are not responsive when authentication is being performed but we do set the socket timeout to 60 seconds. This means that the user will need to wait the full 60 seconds if they cancel after the socket is opened and the server does not respond to the authentication request.
*** Bug 110359 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.