From: J J <1301mail@gmail.com>
To: cygwin@cygwin.com
Subject: SSH key directory defaulting to non-Cygwin SSH client location
Date: Mon, 16 Sep 2013 02:01:00 -0000 [thread overview]
Message-ID: <CAPGcKWv=sHF53Dyuko_dp-gN_nVvPKHqnH+vBD-uBA-Pb1NaSg@mail.gmail.com> (raw)
I recently had to reinstall cygwin on my Windows 7 laptop and am now
having trouble getting passwordless ssh to work from my laptop to
remote hosts. I have another ssh client, Reflections, installed, and
Cygwin insists on using that directory for the ssh key. I would like
to use a separate .ssh directory but can't figure out how to work
around this behavior.
Here's my home directory that the shell opens to. This is also in
/etc/passwd of course:
/home/jd2013 pwd
/home/jd2013
Here's what happens when I try to generate an RSA key file:
/home/jd2013 ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter name for key file: jd2013
C:\Users\jd2013\Documents\Attachmate\Reflection\.ssh\jd2013 already exists.
Overwrite (y/n)? n
I don't know for certain how this was working before I had to
reinstall Cygwin (McAfee had a false positive that bash.exe was a
virus last month), but I would like to avoid having to set my Cygwin
home to the Reflection directory. I tried creating a .ssh subdirectory
in $HOME, but that had no effect. For what it's worth, $HOME is owned
by "jd2013:Domain Users" and the Reflections directory is owned by
"Administrators:Domain Users".
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2013-09-15 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 2:01 J J [this message]
2013-09-16 6:11 ` Christopher Faylor
2013-09-16 19:56 J J
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='CAPGcKWv=sHF53Dyuko_dp-gN_nVvPKHqnH+vBD-uBA-Pb1NaSg@mail.gmail.com' \
--to=1301mail@gmail.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).