From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with ssh-copy-id when home folder contains spaces
Date: Sun, 13 Mar 2016 11:37:00 -0000 [thread overview]
Message-ID: <20160313113726.GF25791@calimero.vinschen.de> (raw)
In-Reply-To: <20160312194552.GC3567@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Mar 12 20:45, Corinna Vinschen wrote:
> On Mar 11 22:38, darkdragon wrote:
> > Some file paths were not correctly escaped. Fix attached ("ssh-copy-id.patch").
>
> Thanks, since we're using the verbatim upstream OpenSSH sources,
> I sent the patch upstream. Hopefully they apply it.
It will be in the next release:
https://bugzilla.mindrot.org/show_bug.cgi?id=2551
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-13 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 21:38 darkdragon
2016-03-12 19:45 ` Corinna Vinschen
2016-03-13 11:37 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160313113726.GF25791@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).