Hello Atsuhiko-san,
I'm sorry I did not understand versioning of sftp protocol
and that recent IETF drafts are not really used yet. I
was only wondering about the version 13 draft that you had
referred me to expiring January 2007 which is already past...
I really appreciate your deep knowledge about all this!
I do understand your hesitation to implement parts
of the protocol which are not yet widely enough accepted,
talking about the "filename-charset" extension.
But this still keeps the original problem around, which
is also acknowledged by the IETF latest draft versions:
* The remote sftpd might not know the encoding used
on the remote side, so conversion to UTF-8 might
be incorrect.
* If converting to UTF-8, the conversion might not
be reversible: there are byte streams which can
not be converted to UTF-8 properly.
Because of these problems, I'd really like to be able
and receive the remote byte streams as-is without
any recoding, such that my client can try and interpret
them properly itself.
But when I understand you right, this is not possible
with a sftp protocol v4 server, since such a server
is always required to translate to UTF-8 ?
I'm wondering what protocol v4 servers are around, and
whether they really stick to that requirement?
Thanks,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -----Original Message-----
> From: Atsuhiko Yamanaka [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 04, 2007 6:01 PM
> To: Oberhuber, Martin
> Cc: [email protected]
> Subject: Re: [JSch-users] Jsch ChannelSftp and character encodings
>
> Hi,
>
> +-From: "Oberhuber, Martin" <[EMAIL PROTECTED]> --
> |_Date: Wed, 3 Oct 2007 15:07:27 +0200 ________________________
> |
> |1. Jsch should allow clients to read the desired remote
> | encoding that was set during version handshake
>
> I guess that you are talking about "filename-charset" extension,
> but it has been only available since sftp protocol 6.
>
> You know that version 6 has been periodicaly updated since
> October 2004
> and I hardly believe that there exists the implemetation on
> this planet
> at the present time. Frankly to say, it is not the good time
> to handle it.
>
> |2. Jsch should allow clients to disable UTF-8 translation
> | when supported by the server
>
> I'm sorry, but 'when supported by the server' is not clear for me.
> I guess that means 'when "filename-charset" extension is
> supported ...'.
>
> |3. Jsch should allow clients to do their own encoding
> | when EITHER protocol version <= 3 OR UTF-8 translation
> | has been disabled in (2)
>
> What do you mean 'their own encoding'?
>
> As far as I have understood, all clients can do is
> just to accept the offer for using some encoding from
> "filename-charset"
> or reject it. For example, if sftpd offers to use "SJIS" encoding
> and the client accept it, the client should use "SJIS" and should not
> use other encoding, for example, "EUC-JP". It seems to me
> you are planning to use other encoding. Have I misunderstood your
> intension?
>
> |When these are implemented, our application will present
> |the server's recommended charset we read in (1) to the
> |user, and if user overrides it we will send the override
> |command in (2) and specify our own encoding in (3).
> |Would that be possible?
>
> As I have written above, I'll not change the code for
> sftp protocol 6 at this time.
>
> By the way, I have finished to modify the code to use
> UTF-8 for filenames internally and added setFilenameEncoding method.
> I have confirmed that Japanese filenames(in UTF-8, SJIS,
> EUC-JP) can be
> transferred by put, get, ls, etc, between WindowsXP and GNU/Linux.
> I have also confirmed that the globing will work for such
> filenames. After some more testing, I'll release it formally.
>
>
> 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: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
