If I modify my config to change Identityfile to something like: Identityfile /cygdrive/c/documents and settings/user/my documents/.ssh/id_rsa process_config_line() of readconf.c just calls strdelim() once so the path will be truncated at the first space. ssh fails with the error that there is garbage at the end of this line.
Can you use DOS-style paths as a workaround, e.g. /docume~1/ This is a bug in the parser though
DOS style pathing, /docume~1/ does work around the parsing of the token at the first space. sorry I haven't provided a patch. I have been too busy. I know. lame.
*** Bug 579 has been marked as a duplicate of this bug. ***
*** Bug 1099 has been marked as a duplicate of this bug. ***
Created attachment 1038 [details] Allow embedded spaces in tokens by preceding with a backslash This patch allows embedded spaces in config tokens by preceding the space with a backslash, eg AllowUsers John\ Smith
Created attachment 1039 [details] Same again with (hopefully) less bugs.
Created attachment 1040 [details] Same again with (hopefully) less bugs.
Created attachment 1041 [details] Fix handling of double-escapes (ie "\\")
This is not specific to Cygwin, but other OSes don't tend to have spaces in either usernames or file paths so it's not usually a problem elsewhere.
(In reply to comment #9) Not true, Mac OS X routinely has spaces appearing in file paths, e.g., bug 579. Harry.
(In reply to comment #10) > Not true, Mac OS X routinely has spaces appearing in file paths, e.g., bug 579. OK, make that "most sane OSes don't tend to..." :-) I've been thinking about it and I think allowing quotes instead would be more logical for people, eg: AllowUsers "John Smith" . When I get a chance I'll change the patch to do this.
Created attachment 1084 [details] Support double-quoting of config arguments Support config directives of the form: User "John Smith" Includes corresponding man page updates (that part of the patch probably won't apply to anything except -current, though).
Patch applied, thanks to all. This will be in 4.4. needs-release-note because it's a user-visible change, albeit a small one.
With the release of 4.4, we believe that this bug is now closed. For information about the release please see http://www.openssh.com/txt/release-4.4 .