[ 
https://issues.apache.org/jira/browse/SSHD-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290995#comment-17290995
 ] 

Thomas Wolf commented on SSHD-1131:
-----------------------------------

There is no hook for this. It's hard-coded in a few places.

The character encoding was not specified in SFTP V3 (version 02 of that IETF 
draft). What protocol version does that Tectia client negotiate with an Apache 
MINA sshd server?

> Filenames containing Norwegian Characters not allowed over SFTP in Tectia 
> client
> --------------------------------------------------------------------------------
>
>                 Key: SSHD-1131
>                 URL: https://issues.apache.org/jira/browse/SSHD-1131
>             Project: MINA SSHD
>          Issue Type: Bug
>            Reporter: Susmit Sarkar
>            Priority: Blocker
>              Labels: mina, sshd
>         Attachments: image-2021-02-24-15-38-39-337.png
>
>
> Hi,
> Filenames containing Norwegian, Spanish, French, and German Characters not 
> allowed over SFTP in Tectia client, names are getting messed up
> How can I override the decoding charset in *SshServer* :
> DecodingCharset is present for SftpClient:
> client.setNameDecodingCharset(Charset.forName("ISO-8859-8"));
> by default it uses UTF-8
> The SftpClient exposes a get/setNameDecodingCharset method which enables the 
> user to modify the charset - even while the SFTP session is in progress 
> After the file is uploaded the Norwegian characters in the filename are 
> replaced with non-readable characters.
> Can we configure the SshServer to override the decoding charset from the 
> default UTF-8? Is there any API to set the SFTP CharsetEncoding (Set the 
> default encoding for filenames in SFTP sessions)
> !image-2021-02-24-15-38-39-337.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to