Bug 483 - scp issues "invalid user name" for a user name containing a blank
Summary: scp issues "invalid user name" for a user name containing a blank
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: scp (show other bugs)
Version: -current
Hardware: All All
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-01 12:02 AEDT by Art Lazanoff
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Art Lazanoff 2003-02-01 12:02:45 AEDT 
scp file "FirstName LastName"@domain.com: produces "invalid user name" but 
ssh "FirstName LastName"@domain.com works. I've seen this error with openssh 
3.5p1, with Irix scp v3.4 and on Solaris scp v3.0.2p1. The presence of a space 
is sufficient to produce the "invalid user name" diagnostic. Sorry but PC users 
often have user names of this form and probably a few Mac users, too.

scp.c contains function okname that issues the "invalid user name" but since it 
really doesn't check with the remote host, scp doesn't really know whether the 
name is OK anyway. Unless there's some other reason for doing this check, I 
recommend just doing away with this function.
Comment 1 Markus Friedl 2003-02-02 21:51:05 AEDT 
fixed for non remote-remote copies.
Comment 2 Damien Miller 2004-04-14 12:24:18 AEST 
Mass change of RESOLVED bugs to CLOSED