Bug 2148

Summary:	failure and crash on non-ASCII characters
Product:	Portable OpenSSH	Reporter:	towo
Component:	sftp	Assignee:	Assigned to nobody <unassigned-bugs>
Status:	REOPENED ---
Severity:	major	CC:	djm, dtucker
Priority:	P5
Version:	6.2p1
Hardware:	Other
OS:	All

Description towo 2013-09-06 01:47:45 AEST

Two issues observed with sftp on Linux and Cygwin:
* If I enter a non-ASCII character (as part of a filename I want to get/put), it is simply ignored, so I cannot transfer such a file.
* If I try to generate the filename by filename completion in sftp, and a file containing a non-ASCII character would be expanded, sftp crashes.

(Severity considered major because this seriously limits handling of a number of files. Also although this is not a security issue, a software crash always suggests a somewhat unsecure feeling to users...)

Comment 1 Darren Tucker 2013-09-06 18:22:03 AEST

the second issue sounds like bug #1990.  probably the first one too.

Comment 2 towo 2013-09-06 22:11:24 AEST

Retestet with latest snapshot on cygwin (after typcial build troubles...):
put xäb works now
put xä^Häb does not: Backspace removes only a byte, not the character!
put x<TAB> does not crash anymore, but does not work either: instead of a completion result, it just appends a few spaces

Comment 3 Damien Miller 2020-01-26 00:45:22 AEDT

Is this still the case? Please reopen this bug if it still affects you?

Comment 4 Damien Miller 2021-03-04 09:54:45 AEDT

close bugs that were resolved in OpenSSH 8.5 release cycle

Comment 5 towo 2021-03-06 20:49:33 AEDT

Retested with sftp 8.5 (on cygwin):
filename completion works and subsequent transmission of files with non-ASCII filenames works,
however, manual entry (including copy/paste) of non-ASCII filename characters still fails, they are silently ignored