On 04/24/2012 01:48 PM, David C. Rankin wrote: > When ssh is called, it reads BOTH /etc/ssh/ssh_config and ~/.ssh/config and > acts accordingly. This means the only reason sftp://hostname fails when ssh is > on a non-standard port is that the sftp:// code is NOT interpreting the ssh > response correctly and is erroneously closing a perfectly good connection that > ssh has established. Basically -- the sftp code just gets stuck waiting on > some response that has changed in the new openssh -- doesn't know what to do > with the response it gets -- and just sits there until it times out with an > error. Tim, I've added a couple of more 'guesses' at where the code can be failing to bug 897. At least to just provide a possible starting point of things to eliminate. -- David C. Rankin, J.D.,P.E.