Your current SFTP protocol version is 3 which lacks many useful features. Would you, please, implement SFTP protocol version 4 (or 5)? It's absolutely nessesary because it supports UTF-8 file names encoding.
s/nessesary/necessary/
We don't have any plans to implement any newer versions of the filexfer drafts, because they introduce too much additional complexity. At present, sftp just passes though whatever the OS sends, so it should cope with UTF8 if both end's filesystems do. If you need more that this, then we are willing to look at extensions to what we have no (there is an extension mechanism in the protocol for this).
s/what we have no/what we have now/
I have the following problem with sftp subsystem - http://winscp.net/forum/viewtopic.php?t=2347
If anyone wants to implement newer versions of the sftp drafts, then please discuss on openssh-unix-dev@mindrot.org. I don't think any of the regular developers have plans in this area though.
Created attachment 1427 [details] Latest and Greatest.. and final sftp tab completion patch. Since OpenSSH moved to libedit with readline like API. The following attachment is the final version of the tab completion patch. This version is being submitting for approval to openssh@ list.
Grr.. Wrong bug.. Sorry.
We won't be supporting more recent versions of the draft-ietf-secsh-filexfer-* drafts. They are hopelessly bloated and broken. If there are specific features that are wanted from the newer drafts we can implement them using the protocol's extension mechanism. Please file separate bugs for these.
Mass update RESOLVED->CLOSED after release of openssh-5.1