https://bugzilla.mindrot.org/show_bug.cgi?id=1632
--- Comment #14 from Marton Balint <c...@fazekas.hu> 2010-01-09 11:27:13 EST --- (In reply to comment #12) > 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. Great! You're right, it's better not to restrict the charset hint to UTF-8. > 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-char...@openssh.com". I agree. > 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-char...@openssh.com", "UTF-8" > > in the SSH_FXP_VERSION packet. Perfect, thanks for the extended patch, charset detection also seems quite useful. Damien, what do you think? -- 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. _______________________________________________ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs