For 2.1 use --with-keygrip.
2.0 does not use the agent for secret key operations but merely as a passphrtase
cache.

Write a script to do that. It is fairly simple; remember to use --status-fd. I
commonly use awk for such tasks.

Well, I rename it as a reminder for the removal.

ok then, feel free to close

Not enough for my case.
You can see here the script where I met the need :
https://gist.github.com/aeris/8483548

I have to verify 3 or more signatures, and need to ensure each from a different
signer.
Using gpgv to do this will be a huge hack with multiple trustedkeys.gpg creation
with a single key inside.
Worst and more complicated solution than my current one (with only one sed).

A « --ensure-signer » option with « gpg --verify » will be definitely simpler
and more secure and robust.
Or I miss something in gpgv.

You may want to look at the gpgv tool instead.

that tool will be removed anyway. It was only used as debug aid and not a real
tools. I don't know how it happened that it eventually was installed.

No we won't do this. IIIRC, there is another rejected bug report and we also
had a discussion at the ML.

I don't think it makes sense to backport it to 1.5 - it has been this way for so
long. Users of 1.5 should upgrade to 1.6.0.

Right, --help displays only a selection of commands. This is on purpose.
gpg --server is not ready for use and you are ready that it should not be
displayed in the help pager either.

I'll go over your list as time permits. Thanks.

--load-extension is a dummy function. It does not do anything.

Yes, please add your information to the webpage, incl. the exact version numbers
and their dependency/relation to IDEA/idea.c/...

For usability reasons, the "load extension" option could check for idea.c
parameter and reject this explicitly in those versions that don't need/support
this anymore. This might be an option in contrast to change all old forum
entries around in the internet discussing this topic.... ;-)
But this would be another bug report, I guess.

Thanks.

GnUPG 2 actually supports IDEA via Libgcrypt and GnuPG also includes IDEA
meanwhile. Thus the whole idea thing does not make anymore sense.

We may eventually update that web page.

Awesome, thank you!

Done something similar for master; needs to be backported to 1.5.

Also related (includes patch): http://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=725411

I have pushed a similar change to 2.0 and master. Will also be done for 1.4.

Werner - taht is the problem - I already tried that (and other hints too) - it
is IMO a lack of a good feature in gpg.

Support is already in master and in the soon to be released 1.6.0

Libgcrypt 1.6 will be released this year.

Retire you old key. There is a "disable" command in "gpg --edit-key".

yep - rather an enhancement request then a bug.

OTOH even before the Snowden-era it would be always better to implemented a
strategy to choose the "best" key (in my case the older has 1024 bit - the newer
has 4096).

Bad news, though that .c/.cpp file exists, it does not seem to get built into
Android. I have tried building against android-14, which is after that file was
introduces, and no luck. I also tried looking for it in the libs, and its not
in the .so or .a libs. Running this gives me nothing:

$ strings /opt/android-ndk/platforms/android-*/arch-arm/usr/lib/* | grep atfork

This has been discussed ad nauseam. Thus this will not be included.

D182: 410_0001-gpg-Compile-time-flag-for-RSA-key-sizes-4096.patch

Uploaded a new patch file - I missed a semicolon.

D183: 407_0001-gpg-Compile-time-flag-for-RSA-key-sizes-4096.patch

Nope; won't be done. We had this in the past and people enabled it and later
complained about disk full stati. And yes, it exposes confidential info.

Tested and works fine with current gnupg and gpgcard.

D180: 398_0001-enable-key-to-card-upload-for-cert-only-keys.patch

D181: 389_cert_card.patch

Ah well, the Spansih versions have been dropped. The Howtos are anyway somewhat
outdated.

I took copies of the MiniHowto from archive.org and put them direct under GnuPG.org.

This is not a worth a bug report. If you want to discuss this topic, please use
the gnupg-users mailing list. We can't answer indivdual questions by means of a
bug tracker.