Bug 159590 – app-crypt/pinentry - keywords request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Alon Bar-Lev (RETIRED) 2006-12-31 10:59:47 UTC]

Hello,

I want app-crypt/gnupg-2* to have app-crypt/pinentry dependency.

Missing keywords:
- arm
- s390
- sh

Thanks!

[Comment 1 Alon Bar-Lev (RETIRED) 2006-12-31 11:46:17 UTC]

No need s390.

[Comment 2 Robin Johnson 2007-01-04 16:32:09 UTC]

arm/sh (vapier): please consider this high priority.

alonbl: why no s390? pinentry will be installed always with gnupg, not just with USE=X.

[Comment 3 Alon Bar-Lev (RETIRED) 2007-01-05 01:21:01 UTC]

I thought we should automatically merge pinentry if USE X on gnupg, not always...
Do you think that we should always merge pinentry if gnupg is merged?

[Comment 4 Robin Johnson 2007-01-05 01:35:44 UTC]

alonbl: gpg-agent explictly calls pinentry (see agent/call-pinentry.c). Ergo it should always be installed, otherwise the agent fails.

[Comment 5 Alon Bar-Lev (RETIRED) 2007-01-05 03:25:39 UTC]

I thought people may use:
/usr/libexec/gpg-preset-passphrase

I was not aware that it is used for same console.
Adding back s390.

Thanks!

[Comment 6 Robin Johnson 2007-01-05 08:44:02 UTC]

# emerge --unmerge pinentry
...
# emerge =gnupg-2.0.1-r2
...
# (generate a test key)
# gpg --armour --sign <diff

You need a passphrase to unlock the secret key for
user: "Robin2 <root@buck-int.2>"
4096-bit RSA key, ID C2EE028D, created 2006-05-19 (main key ID 5B689C16)

gpg: DBG: connection to agent established
gpg: problem with the agent: No pinentry
gpg: Invalid passphrase; please try again ...

You need a passphrase to unlock the secret key for
user: "Robin2 <root@buck-int.2>"
4096-bit RSA key, ID C2EE028D, created 2006-05-19 (main key ID 5B689C16)

gpg: problem with the agent: No pinentry
gpg: Invalid passphrase; please try again ...

You need a passphrase to unlock the secret key for
user: "Robin2 <root@buck-int.2>"
4096-bit RSA key, ID C2EE028D, created 2006-05-19 (main key ID 5B689C16)

gpg: problem with the agent: No pinentry
gpg: no default secret key: Bad passphrase
gpg: signing failed: Bad passphrase


And doing an strace does show that it is trying to exec pinentry.

[Comment 7 Alon Bar-Lev (RETIRED) 2007-01-05 08:50:47 UTC]

As far as I understand you use /usr/libexec/gpg-preset-passphrase after the agent is up...
But OK... I added s390... :)

[Comment 8 Robin Johnson 2007-01-05 09:29:14 UTC]

alonbl:
gpg-preset-passphrase is meant for user interaction with the agent yes, but the problem I listed there was in the default behavior of the agent when the passphrase was not yet cached. It invoked (or at least tried) pinentry.

arm, s390, sh:
target keywords for you to add KEYWORDS="~arm ~s390 ~sh"

[Comment 9 Jakub Moc (RETIRED) 2007-01-14 14:09:14 UTC]

*** Bug 162045 has been marked as a duplicate of this bug. ***

[Comment 10 Alon Bar-Lev (RETIRED) 2007-01-23 20:59:27 UTC]

[ping]

[Comment 11 Alon Bar-Lev (RETIRED) 2007-01-31 23:08:18 UTC]

I will add the pinentry dependency breaking arm, s390, sh...
Soon...
So all other user may get a stable environment.

[Comment 12 Robin Johnson 2007-01-31 23:21:36 UTC]

Alonbl, it is done already, just looks like the bug didn't get updated.

# earch
pinentry-0.7.2-r2[0]: amd64 x86
pinentry-0.7.2-r3[0]: alpha ~amd64 arm hppa ia64 mips ppc ppc64 s390 sh sparc ~x86 ~x86-fbsd