If a shell or exec session to an F-Secure (AKA, "WRQ") server is terminated prematurely after authentication and after the "shell" or "exec" packet is sent, either because the server is misconfigured or it rejects the session, the OpenSSH client will hang. Either the server process or the client process must be manually killed.
Could you please attach a debug log from a ssh client exhibiting this problem?
Created attachment 1112 [details] This is a session to Tru64 UNIX This is a log from Fedora Core 5 to Tru64 UNIX running the F-Secure server. I can readily replicate with the same server on OpenVMS. The key here is that the server has the SessionRestricted subsystem flag set.
I don't see anything in this log that indicates that an error has occurred, which probably means that the remote end is not informing the client. If this is the case, I don't think there is anything we can do here. Does setting ServerAliveInterval and ServerAliveCountMax help?
one year, no reply == bug closed
Mass update RESOLVED->CLOSED after release of openssh-5.1