162045 – gnupg-2 (and 1.9?) should depend on pinentry

Bug 162045 - gnupg-2 (and 1.9?) should depend on pinentry

Summary: gnupg-2 (and 1.9?) should depend on pinentry

Status:	RESOLVED DUPLICATE of bug 159590

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-01-14 14:06 UTC by Marti Raudsepp
Modified:	2007-01-14 14:09 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marti Raudsepp 2007-01-14 14:06:34 UTC

This is what I get when attempting to gpg --clearsign with gnupg-2.0.1-r2:

You need a passphrase to unlock the secret key for
user: #####
####-bit RSA key, ID ########, created ####-##-## (main key ID ########)

gpg: DBG: connection to agent established
gpg-agent[25299]: can't connect server: `ERR 67109133 can't exec `/usr/bin/pinentry': No such file or directory'
gpg-agent[25299]: can't connect to the PIN entry module: IPC connect call failed
gpg-agent[25299]: command get_passphrase failed: No pinentry
gpg: problem with the agent: No pinentry
gpg: Invalid passphrase; please try again ...


After installing app-crypt/pinentry, the problem naturally goes away.

This was already reported in bug 60809, however gnupg 1.9 is now stable/supported and pinentry is also stable. And from what I can tell, gnupg 2.0 no longer accepts passphrases from the command line at all, and requires /usr/bin/pinentry -- at least by default.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2007-01-14 14:09:14 UTC

Needs to be keyworded first...


*** This bug has been marked as a duplicate of bug 159590 ***