[Bug 2966] scp rev 1.202 fix doesn't quite hit the mark

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Mon Feb 11 17:34:54 AEDT 2019


Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
                 CC|                            |djm at mindrot.org

--- Comment #1 from Damien Miller <djm at mindrot.org> ---
Thanks - the changes in rev 1.202 weren't complete, e.g. they don't
include support for {foo,bar} alternations. I've committed a fix that
also corrected the paths-without-slash problem along the way.

I'll take a look at the space-separated path thing; it might be
difficult to discern a space-separated source path that refers to
multiple files from one that refers to a single file with spaces in its
name. It really depends on the server's rules, and the client has no
way of knowing these.

In practice, /bin/sh is likely to be doing the dequoting/expansion,
except when it isn't.

You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

More information about the openssh-bugs mailing list