openssh bugs - Feb 2006 - [Bug 1164] scp with spaces username no longer works

http://bugzilla.mindrot.org/show_bug.cgi?id=1164

           Summary: scp with spaces username no longer works
           Product: Portable OpenSSH
           Version: 4.3p2
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: scp
        AssignedTo: bitbucket at mindrot.org
        ReportedBy: dtucker at zip.com.au


In 4.2 and below, both of the following work even though they have spaces in
the username:
1) scp "user name at host:/path" /path
2) scp /path "user name at host:/path"

This doesn't work (and can't reliably since it effectively does
"ssh host1 scp
/path user name at host2:/path" so relies on the remote shell):
3) scp "user name at host1:/path" "user name at host2:/path"

In 4.3, 1) still works but 2) doesn't:
$ scp /path "user name at localhost:/path"
user name: invalid user name

I will attach a patch to fix this.  It should allow 1) and 2) while still
disallowing 3).




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1164





------- Comment #1 from dtucker at zip.com.au  2006-02-26 16:04 -------
Created an attachment (id=1085)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=1085&action=view)
Allow spaces in scp usernames

$ scp "user name at localhost:/path" /path
user name at localhost's password:
$ scp /path "user name at localhost:/path"
user name at localhost's password:
$ scp "user name at localhost:/path" "user name at
localhost:/path"
user name: invalid user name

Also fixes a leak of "arg".




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1164





------- Comment #2 from djm at mindrot.org  2006-03-12 15:11 -------
(From update of attachment 1085)
the patch looks sane, but i don't quite see how it fixes the problem...




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.