*New 11.3 series Release:
2019-10-19: XigmaNAS 11.3.0.4.7014 - released

*New 12.0 series Release:
2019-10-05: XigmaNAS 12.0.0.4.6928 - released!

*New 11.2 series Release:
2019-09-23: XigmaNAS 11.2.0.4.6881 - released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

SFTP connection - Encoding Mismatch Giving Wrong File Names

Secure shell connections.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
natessh123
NewUser
NewUser
Posts: 1
Joined: 21 Jun 2017 21:30
Status: Offline

SFTP connection - Encoding Mismatch Giving Wrong File Names

#1

Post by natessh123 » 22 Jun 2017 14:59

I have a problem with a java SFTP connection to a file repository returning incorrect file names. I believe an incorrect encoding on the SSH installation on the AIX 7.1 system may be the culprit. Can anyone tell me a method to confirm the encoding in use by the SSH (or recommend another fix)?
Example:
Correct: testmodel123±±±xyz.model
Displayed: testmodel123???xyz.model

The java code I'm using with the vfs 2.1 library is set up to use the UTF-8 encoding when reading file names (using the SftpFileSystemConfigBuilder class setFileNameEncoding() method), but on one machine we consistently get errors where special characters are returned as "?"s, ultimately giving us the wrong names. Since on some other machines we're getting correct results, the solution must be elsewhere, specifically in the SSH installation itself, as this is showing that the name is reaching us with the wrong name before we have a chance in java to "ask for the UTF-8 version" of the file name, so to speak.

To reiterate, we have two setups, both using Windows Server 2012 R2 Standard OS attempting an SFTP connection to different AIX 7.1 OS machines. In one case, the file names are returned correctly. In the other, we get incorrectly encoded file names (it seems). An SSH encoding issue seems like the likely culprit. Does anyone have any suggestions for possible solutions?

Post Reply

Return to “SSH”