unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marco van Hulten <marco@hulten.org>
To: help-guix@gnu.org
Subject: Re: gpg-agent error: No pinentry
Date: Thu, 19 Dec 2019 10:02:40 +0100	[thread overview]
Message-ID: <20191219100240.3b404ba9@jasniac.instanton> (raw)
In-Reply-To: <20191219092258.30cccce4@jasniac.instanton>

[-- Attachment #1: Type: text/plain, Size: 2449 bytes --]

correction follows inline—

Any help is appreciated.

Je 19 dec 09:22 skribis Marco:
> Je 18 dec 22:50 skribis Andreas:
> > On Wed, Dec 18, 2019 at 10:41:27PM +0100, Marco van Hulten wrote:  
> > > Do I need to do any more actions accept for 'guix package -i gnupg
> > > pinentry'?    
> > 
> > I also have a file .gnupg/gpg-agent.conf in my home directory
> > containing the following lines:
> > 
> > default-cache-ttl 300
> > max-cache-ttl 3600
> > pinentry-program /home/USERNAME/.guix-profile/bin/pinentry-curses  
> 
> Thank you, Andreas and Gábor, very useful to know that pinentry-program
> should be set.  I did so:
> 
> $ file $(realpath $(grep ^pinentry-program ~/.gnupg/gpg-agent.conf | awk '{print $2}'))
> /gnu/store/12gagy0ql4v7qlv9px54lz5fy4d7gff9-pinentry-tty-1.1.0/bin/pinentry-tty:
> ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked,
> interpreter /gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/lib/ld-linux-x86-64.so.2,
> for GNU/Linux 2.6.32, not stripped
> 
> Importing a public and private key pair, following [1], worked properly
> now, but it still complains when decrypting a file.
> 
> [1]: https://www.debuntu.org/how-to-importexport-gpg-key-pair/
> 
> To be sure, if I now try to remove the key, 'gpg --delete-key publiko',
> it says that I need to use option "--delete-secret-keys" to delete the
> private key first.  So it appears to be really there.  However,
> 
>     $ date | gpg -e > jadaja.gpg
>     gpg: encrypted with 4096-bit RSA key, ID 54AE7D44B93BDBDF, created 2019-05-30
>           "Marco van Hulten (publiko) <marco@hulten.org>"
>     gpg: public key decryption failed: No pinentry
>     gpg: decryption failed: No secret key

Sorry, the lines were not copied consistently.  Now the whole
encryption/decryption process verbatimly copied from my terminal:

    $ date > test.txt
    $ gpg --output test.txt.gpg --encrypt --recipient marco@hulten.org test.txt
    $ gpg --decrypt test.txt.gpg 
    gpg: encrypted with 4096-bit RSA key, ID 54AE7D44B93BDBDF, created 2019-05-30
          "Marco van Hulten (publiko) <marco@hulten.org>"
    gpg: public key decryption failed: No pinentry
    gpg: decryption failed: No secret key

> I tried killing gpg-agent to be sure it uses the current configuration,
> but again it complains about pinentry.
> 
> Apropos, I this e-mail is signed with this very key.
> 
> —Marco

[-- Attachment #2: OpenPGP digitale handtekening --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-12-19  9:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 21:41 gpg-agent error: No pinentry Marco van Hulten
2019-12-18 21:50 ` Andreas Enge
2019-12-19  8:22   ` Marco van Hulten
2019-12-19  9:02     ` Marco van Hulten [this message]
2019-12-20  9:49       ` Marco van Hulten
2019-12-20 19:12         ` Gábor Boskovits
2019-12-20 21:15           ` Marco van Hulten
2019-12-18 21:52 ` Gábor Boskovits

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191219100240.3b404ba9@jasniac.instanton \
    --to=marco@hulten.org \
    --cc=help-guix@gnu.org \
    /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).