similar to: scp and character encoding in file names

I've experienced some troubles using scp with remote files with spaces, amphersands or parantheses in their filenames on Linux hosts. This happens: stain at false:~$ scp "bender.linpro.no:blapp blapp" . scp: blapp: No such file or directory scp: blapp: No such file or directory stain at false:~$ scp "bender.linpro.no:blapp&blapp" . bash: blapp: command

I have not been able to get scp(1) to download a file with a newline in its name. I know that scp(1) requires that remote filenames be escaped for the shell, but that leads to protocol errors. I am also unable to get sftp(1) to handle such files. It fails with an ?unterminated quoted argument? error, no matter how I try to quote the newline. Furthermore, the SFTP CLI is not well-suited to

On Mon, 4 Nov 2019, David Newall wrote: > On 4/11/19 3:29 am, Demi M. Obenour wrote: > > I have not been able to get scp(1) to download a file with a newline > > in its name. I know that scp(1) requires that remote filenames be > > escaped for the shell, but that leads to protocol errors. > > I see something much worse: > > $ sudo sh > # echo

http://bugzilla.mindrot.org/show_bug.cgi?id=1265 Summary: SCP progress doesn't map to standard out or standard error Product: Portable OpenSSH Version: 4.4p1 Platform: PPC OS/Version: AIX Status: NEW Severity: minor Priority: P4 Component: scp AssignedTo: bitbucket at

https://bugzilla.mindrot.org/show_bug.cgi?id=2193 Bug ID: 2193 Summary: Scp sometimes breaks non-ASCII filenames in copying progress indicator Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component: scp

http://bugzilla.mindrot.org/show_bug.cgi?id=957 Summary: Shell special characters not escaped by scp Product: Portable OpenSSH Version: 3.9p1 Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: greenrd

http://bugzilla.mindrot.org/show_bug.cgi?id=804 Summary: Locale character encoding disobeyed on interactive session Product: Portable OpenSSH Version: 3.8p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: minor Priority: P4 Component: ssh AssignedTo: openssh-bugs at

http://bugzilla.mindrot.org/show_bug.cgi?id=472 Summary: scp won't accept 'hash' character in usernames, ssh will Product: Portable OpenSSH Version: 3.5p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=852 Summary: scp bug with computer names Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: johnw.nicholson at

https://bugzilla.mindrot.org/show_bug.cgi?id=2192 Bug ID: 2192 Summary: scp output alignment bug with UTF-8/multibyte sequences Product: Portable OpenSSH Version: 6.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: scp

http://bugzilla.mindrot.org/show_bug.cgi?id=424 Summary: scp mishandles files with spaces in names Product: Portable OpenSSH Version: older versions Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-unix-dev at mindrot.org

On Sun, Nov 03, 2019 at 06:37:57AM -0500, Michael Lueck via samba wrote: > I have Samba shares mounted to my Linux workstation. Mostly I access files on the Samba server over the Samba mount. I use mount.cifs to bring up these mounts. > > For a couple of special cases, I use scp to transfer files between the > server and workstation. Special characters in filenames give sending them

https://bugzilla.mindrot.org/show_bug.cgi?id=1998 Bug #: 1998 Summary: Arbitrary command execution using SCP Classification: Unclassified Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: Linux Status: NEW Severity: security Priority: P2 Component: scp AssignedTo:

Hi all, Please pardon me if this has been discussed already on this list. I searched on "destination" and did not find a hit. The problem I am trying solve is having backups on a remote server that even root cannot not read. I have seen lot's of specialized file systems and volume drivers for various operating systems. But being that all files are already scp'd to the

http://bugzilla.mindrot.org/show_bug.cgi?id=992 Summary: scp cannot handle filenames with spaces in them Product: Portable OpenSSH Version: 3.9p1 Platform: All OS/Version: All Status: NEW Keywords: patch Severity: normal Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org

Hi, I just made a patch to "correctly" support special characters in scp at the remote side. First let me explain the problem: # cd /tmp # touch this is a test # cp this\ is\ a\ test a\ test # scp localhost:$PWD/a\ test this\ is\ a\ test scp: /tmp/a: No such file or directory scp: test: No such file or directory but # scp localhost:$PWD/a\\\ test this\ is\ a\ test a test

http://bugzilla.mindrot.org/show_bug.cgi?id=852 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From dtucker at zip.com.au 2004-09-11

http://bugzilla.mindrot.org/show_bug.cgi?id=472 ------- Additional Comments From chuzwuzza at optusnet.com.au 2003-01-23 17:15 ------- Created an attachment (id=207) --> (http://bugzilla.mindrot.org/attachment.cgi?id=207&action=view) Patch to allow 'hash' character in scp usernames ------- You are receiving this mail because: ------- You are the assignee for the bug, or

On Mon, 4 Nov 2019 at 14:07, David Newall <openssh at davidnewall.com> wrote: > [about scp] That's just awful, and I should have > thought it was not at all necessary. Am I missing something? > If you're saying that the scp protocol is an unfixable mess then the openssh team has been agreeing[0] with you for at least a decade and a half. We fix what we can, but some

X-PMC-CI-e-mail-id: 13726 Hi, I have been a successful user of Openssh for some time. I am attaching two articles from BugTraq. Hopefully, they show exactly the security problems reported in the BugTraq mailing list. [Pity that no one seemed to have bothered to contact the mailing list(s) for openssh development.] I am not sure what the right fixes would be. But at least, people need to be