public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Garber, Dave (GE Oil & Gas, Non-GE)" <dave.garber1@ge.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: problem with gnupg2 not prompting for passphrase
Date: Tue, 11 Jul 2017 18:10:00 -0000	[thread overview]
Message-ID: <CY4P101MB0214B15068E2112AE15A61B6BFAE0@CY4P101MB0214.NAMP101.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <155948c1-1a82-b033-2322-f9f8f62c17c4@jeffunit.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2824 bytes --]



> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of jeff
> Sent: Tuesday, July 11, 2017 1:56 PM
> To: cygwin@cygwin.com
> Subject: EXT: Re: problem with gnupg2 not prompting for passphrase
> 
> On 7/11/2017 10:51 AM, Brian Inglis wrote:
> > On 2017-07-10 23:07, Thomas Wolff wrote:
> >> Am 11.07.2017 um 00:38 schrieb jeff:
> >>> On 7/10/2017 1:21 PM, Achim Gratz wrote:
> >>>> jeff writes:
> >>>>> jeff_xeon:/cygdrive/u:503: gpg2 --output fred.good --decrypt
> >>>>> fred.gpg
> >>>>> gpg: encrypted with 4096-bit RSA key, ID A3791E7DD935A424, created
> >>>>> 2013-03-21
> >>>>>        "Jeff Deifik <jeff@jeffunit.com>"
> >>>>> gpg: public key decryption failed: No such device or address
> >>>>> gpg: decryption failed: No secret key
> >>>>>
> >>>>> I have uninstalled the standalone version of gnupg2 before I did this.
> >>>>> It seems most likely that the version of gpg2 being invoked is a
> >>>>> cygwin version.
> >>>> It fails to find your private key, so it is quite obviously not in
> >>>> a place where gpg2 expects to find it.
> >>> I have my keys stored in $HOME/.gnupg which is where gnupg v1
> expects them.
> >
> > gnupg2 uses the same --homedir paths, $GNUPGHOME env var, native
> > Windows reg key, and native Windows portable apps homedir as gnupg1.
> >
> >> Just guessing: Some software does not look in $HOME for config files (e.g.
> >> openssh) but expects them in /home/...
> >
> > OpenSSH expects user config files in ~/.ssh/ where ~ is $HOME, or the
> > home directory from "getent passwd $LOGNAME", which defaults to /.
> >
> > They'd better expect $HOME, not /home/$LOGNAME, as $HOME could
> also be
> > /u/$LOGNAME, /mnt/nfs/OrkeyDorkey, or /mnt/Network\ Users/Orkey\
> > Dorkey! ;^>
> >
> 
> The problem almost certainly lies with pinentry. It seems to be a new feature

See https://sourceware.org/ml/cygwin/2017-07/msg00100.html for the solution.

> of gnupg2. As I demonstrated, there is no problem finding my public key, nor
> my private key, which are located in the default place.
> The problem is the method used to get the passphrase is very broken.
> After reading some stuff via google, I added
> 
> GPG_TTY=$(tty)
> export GPG_TTY
> 
> to my .bashrc file, with no observable changes.
> 
> jeff
> 
> 
> --
> 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

\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2017-07-11 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 14:30 jeff
2017-07-10 19:42 ` Thomas Wolff
2017-07-10 19:55   ` jeff
2017-07-10 20:21     ` Achim Gratz
2017-07-10 22:38       ` jeff
2017-07-11  5:07         ` Thomas Wolff
2017-07-11 17:51           ` Brian Inglis
2017-07-11 17:56             ` jeff
2017-07-11 18:10               ` Garber, Dave (GE Oil & Gas, Non-GE) [this message]
2017-07-11 18:18                 ` jeff

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=CY4P101MB0214B15068E2112AE15A61B6BFAE0@CY4P101MB0214.NAMP101.PROD.OUTLOOK.COM \
    --to=dave.garber1@ge.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).