gnupg/pinentry not aware of each other

  • Done
  • quality assurance status badge
Details
4 participants
  • Alexandre Hannud Abdo
  • Brice Waegeneire
  • jon
  • Martin Becze
Owner
unassigned
Submitted by
jon
Severity
important
Merged with
J
J
jon wrote on 2 Sep 2019 06:56
(address . bug-guix@gnu.org)
b7a57a2e366a94aa9cf07a893899bccf@dorsal.tk
$ gpg --full-generate-key
<snip>
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry
$ which pinentry
/run/current-system/profile/bin/pinentry
M
M
Martin Becze wrote on 18 Sep 2019 11:41
(address . jon@dorsal.tk)
8554f6221dc9c056b93a4bdee7638d48@riseup.net
On 2019-09-02 04:56, jon@dorsal.tk wrote:
Toggle quote (12 lines)
> $ gpg --full-generate-key
> <snip>
> Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
> We need to generate a lot of random bytes. It is a good idea to perform
> some other action (type on the keyboard, move the mouse, utilize the
> disks) during the prime generation; this gives the random number
> generator a better chance to gain enough entropy.
> gpg: agent_genkey failed: No pinentry
> Key generation failed: No pinentry
> $ which pinentry
> /run/current-system/profile/bin/pinentry

try added `pinentry-program /home/USER/.guix-profile/bin/pinentry-gtk-2`
to `~/.gnupg/gpg-agent.conf`
let me know if that works. I also encountered this.
B
B
Brice Waegeneire wrote on 20 Mar 2020 17:00
merge 37266 36784
(address . control@debbugs.gnu.org)
e8ff57377c8b7ad8062683ee07881da0@waegenei.re
severity 37266 important
merge 37266 36784
quit
B
B
Brice Waegeneire wrote on 20 Mar 2020 21:36
merge 37266 24076
(address . control@debbugs.gnu.org)
b767d0eb10e4a8c78b1ad74488c636be@waegenei.re
severity 24076 important
merge 37266 24076
quit
A
A
Alexandre Hannud Abdo wrote on 22 Apr 2021 23:43
(address . control@debbugs.gnu.org)
8c9825b8e41f4dcfd9ecd9f0351b3d73eebee325.camel@member.fsf.org
unarchive 24076
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQ4aRTDkc5D704CYnMQUI+lk7e+bQUCYIHuHAAKCRAQUI+lk7e+
badoAJwJdK4XrqTpviE7KTetMMG2GhOWGwCdG6OE73MnZUfQu32I0Lj8OydxmYo=
=2Z9Z
-----END PGP SIGNATURE-----


?
Your comment

This issue is archived.

To comment on this conversation send an email to 37266@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 37266
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch