Bug 1099

Summary:	usernames in config file cannot contain space
Product:	Portable OpenSSH	Reporter:	David Monniaux <David.Monniaux>
Component:	ssh	Assignee:	Assigned to nobody <unassigned-bugs>
Status:	CLOSED DUPLICATE
Severity:	normal
Priority:	P2
Version:	4.1p1
Hardware:	Other
OS:	Linux

Description David Monniaux 2005-10-10 07:56:51 AEST

I would like to define an entry in ~/.ssh/config for a Windows machine, where the username contains a space.

Neither
user foo bar
nor
user "foobar"
work.

Comment 1 Darren Tucker 2005-12-13 19:24:18 AEDT

This is a dupe of bug #482.  The workaround is to use the 8.3 name ("userna~1") for the directory.

The parser need to learn how to either escape spaces (John\ Smith), understand quotes ("John Smith") or both.

*** This bug has been marked as a duplicate of 482 ***

Comment 2 Darren Tucker 2005-12-21 00:11:17 AEDT

Oops, I see that the issue is the username not a pathname containing a username, which means the workaround is bogus.  There's a patch attached to bug #482 which makes the parser allow spaces prefixed by a "\".  Your example would be:

User foo\ bar

Having thought about it, though, I think using quotes instead would be more logical.  At some point I'll hang another diff on bug #482 to do this.

Comment 3 Darren Tucker 2006-10-07 11:42:43 AEST

Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.