[Bug 1632] [PATCH] UTF-8 hint sftp-server extension

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=1632

--- Comment #12 from Salvador Fandiño <sfandino at yahoo.com> 2010-01-09 01:26:48 EST ---
(In reply to comment #10)
> Yes, charset problems may also arise between UNIX systems. The ultimate
> solution would be the filename-charset extension, but as far as I know
> that would require SFTP protocol version 6, which is not going to
> happen in openSSH in the near future.

it is an *extension* so you can add it to implementations of previous
protocol versions as long as no conflicts arise.

> Of course, if that's more acceptable I may recreate my patch, to give
> hint not just for utf-8 encoding, but for the encoding of your choice.
> But implementing the filename-charset extension seems too complicated
> to me, because that would require protocol version 6, in-server charset
> conversion, etc...

The filename-charset extension just tells the client the character
encoding used on the filesystem. We don't need to perform any character
conversion on the server.

Anyway, just to be sure that no client gets confused by the slighly
different semantics (as v6 requires the client to ask for deactivation
of the local-encoding-to-utf8 conversion) we can name the extension as
"filename-charset at openssh.com".

I have just attached a patch that adds support for a new flag allowing
to set the encoding on the server. In example:

  sftp-server -s UTF-8

will cause clients to get the pair

  "filename-charset at openssh.com", "UTF-8"

in the SSH_FXP_VERSION packet.

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.