- User Since
- Mar 27 2017, 4:49 PM (120 w, 2 d)
Feb 6 2014
Jan 31 2014
This happens because AM_PATH_GPG_ERROR uses AC_ARG_WITH
in a bad way. First it parses the official name, which
is --with-libgpg-error-prefix. But then it tries to implement
a fallback to the old undocumented option name
--with-gpg-error-prefix. Unfortunately, that fallback
unconditionally overwrites the result of the first
The enclosed patch fixes this issue.
This patch needs to be installed in both the libksba
and the gnupg repositories.
The same issue was however fixed in the libassuan repo
in 97ce28a430129ce997783c6196ccfe737f5b3007. Applying
that solution in the libksba and gnupg repos would work
just as fine as my patch (and reduce the proliferation
of differing versions).
I think T1526 is a duplicate of this bug.
I think T1561 is the same bug, but in the gnupg
I was not aware that the subkey can have a different passphrase. That
does indeed complicate things.
I like your idea to tell gpg-agent about related keys. I think that would
solve the problem. (I did look at the existing feature requests but did
not find a duplicate.)
I attach a small shellscript that demonstrates the problem. It must be run in an
environment where no agent is running. This has been tested under Ubuntu Linux.
If prompted for a passphrase, use "abc". Please read the script before running it.
Dec 19 2013
Awesome, thank you!
Dec 4 2013
Still have this issue.
The patch against 2.0.19 applies to 2.0.22, bumping the version.
I will try again on both mailing lists, as well.
Mar 6 2013
Still have this issue. Here is an updated patch against 2.0.19. Please
consider including it, or provide some feedback if this is a bad idea / should
be done a different way.
Marking this as a bug since it restores useful functionality that was lost.
Feb 8 2012
Nov 17 2009
May 28 2009
On Thu, May 28, 2009 at 03:03:07PM -0000, Werner Koch via BTS wrote: