From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
Subject: Re: Still unable to 'git push' or ssh to sourceware -- resolved
Date: Thu, 12 Nov 2015 09:22:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.63.1511120114290.38016@m0.truegem.net> (raw)
In-Reply-To: <20151110092122.GA7017@calimero.vinschen.de>
On Tue, 10 Nov 2015, Corinna Vinschen wrote:
> You're missing something important. The key you sent to sware and the
> other key you sent to the cygwin-apps list are both the public part of
> your keys. This public part of a key *never* requires a passphrase.
> After all it's supposed to be readable by everyone, right?
>
> If ssh asks for a passphrase, it's your local, *private* key which is
> encrypted using this passphrase. Therefore this has nothing to do with
> ssh on the remote machine. It can't require passphrases since,
> obviously, it doesn't know your private key. The private key never
> leaves your local machine. So this asking for a passphrase is a local
> problem on your machine which you would have to fix locally.
>
> Btw., I never saw the problem that a local key without passphrase results
> in ssh asking for a passphrase. The difference in the keyfile (encrypted
> vs. non-encrypted) is obvious to ssh:
>
> $ head -2 .ssh/my_key
> -----BEGIN RSA PRIVATE KEY-----
> Proc-Type: 4,ENCRYPTED
Many thanks for this correction to my broken mental model of passphrases
vs passwords. Between these nuggets-o-knowledge and a fix to my
~/.ssh/config (i.e. IdentityFile *must* refer to a private key file) I was
able to 'git push' my cygutils updates to sourceware with my original key.
I am now debugging a revised cygutils.cygport and figuring out where I can
host the updated tar.xz packages for review. I've got a place in mind.
Thanks again,
..mark
prev parent reply other threads:[~2015-11-12 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 1:54 Still unable to 'git push' or ssh to sourceware Mark Geisert
2015-11-10 4:47 ` Yaakov Selkowitz
2015-11-10 5:03 ` Mark Geisert
2015-11-10 9:21 ` Corinna Vinschen
2015-11-12 9:22 ` Mark Geisert [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=Pine.BSF.4.63.1511120114290.38016@m0.truegem.net \
--to=mark@maxrnd.com \
--cc=cygwin-apps@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).