Page MenuHome GnuPG

gpg-agent[11104]: can't connect to the PIN entry module:
Closed, ResolvedPublic

Description

Getting below error after installation of GunPGP in Sun Solaris by Admin team.
While try to register keys getting error.
gpg2 --gen-key
gpg (GnuPG) 2.0.16; Copyright (C) 2009 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Warning: using insecure memory!
gpg: keyring `/export/users/applprod/.gnupg/secring.gpg' created
Please select what kind of key you want:

(1) RSA and RSA (default)
(2) DSA and Elgamal
(3) DSA (sign only)
(4) RSA (sign only)

Your selection? 3
DSA keys may be between 1024 and 3072 bits long.
What keysize do you want? (2048)
Requested keysize is 2048 bits
Please specify how long the key should be valid.

   0 = key does not expire
<n>  = key expires in n days
<n>w = key expires in n weeks
<n>m = key expires in n months
<n>y = key expires in n years

Key is valid for? (0) 0
Key does not expire at all
Is this correct? (y/N) y

GnuPG needs to construct a user ID to identify your key.

Real name: CDFPGP
Email address:
Comment: test for pgp2
You selected this USER-ID:

"CDFPGP (test for pgp2)"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
You need a Passphrase to protect your secret key.

gpg-agent[3990]: can't connect to the PIN entry module: IPC connect call failed
gpg-agent[3990]: command get_passphrase failed: No pinentry
gpg: problem with the agent: No pinentry
gpg: Key generation canceled.

Details

Version
2.0.16

Event Timeline

RKBHALLA set Version to 2.0.15.
RKBHALLA added a subscriber: RKBHALLA.
werner lowered the priority of this task from High to Normal.Sep 17 2010, 4:17 PM

Do you have a pinentry installed? Depending on your configuraion the default is
either /usr/bin/pinentry or /usr/local/bin/pinentry. If for some reason you
can't use that, you may put a line

pinentry-program /full/name/of/pinentry

into ~/.gnupg/gpg-agent.conf.

werner changed Version from 2.0.15 to 2.0.16.Sep 17 2010, 4:19 PM

This sounds like a user configuration problem. Given Werner's reply, the lack
of response from the reporter and the amount of time that has gone by, I'm
closing this.

neal claimed this task.