Hi, +-From: "Oberhuber, Martin" <[EMAIL PROTECTED]> -- |_Date: Wed, 26 Sep 2007 13:15:20 +0200 _______________________ | | >> | - provide a ChannelSftp.setControlEncoding() |As you mentioned yourself, there are SSH servers (e.g. OpenSSH) |which do not recode the arguments of commands from UTF-8 to |the locally used encoding -- they simply take the byte stream |they read from a command (e.g. stat()) and pass it to the OS. |As a result, on a system where no recoding happens and a user |can not or does not want to use UTF-8 for file and directory |path encoding, the user needs to be able to specify the encoding |that Jsch should use when sending file and path names. Only with |custom selected encoding can the user produce the right byte |stream for file and path names that the remote side needs.
Frankly to say, I have hesitated to add such an API, which expects the sftpd's noncompliances to the sftp protocol[1]. Other sftpd implementations may have supported it correctly and OpenSSH may suddenly change its implementation in the future. I think that the proposed method may become the source of the trouble. If that method is added, are you really planning to use it in your product? It must be easy to add that method, but I really worry about the result. [1] http://tools.ietf.org/html/draft-ietf-secsh-filexfer-13 Sincerely, -- Atsuhiko Yamanaka JCraft,Inc. 1-14-20 HONCHO AOBA-KU, SENDAI, MIYAGI 980-0014 Japan. Tel +81-22-723-2150 +1-415-578-3454 Fax +81-22-224-8773 Skype callto://jcraft/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ JSch-users mailing list JSch-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jsch-users
