Not a problem in 1.4

Suggest asking for operational help on gnupg-users@gnupg.org.

This was a Debian-specific problem with their unstable
package, and has since been fixed.

GnuPG 1.0.6 is many years out of date. Please re-try with
the current version (1.2.6).

I believe this is a (currently fixed) problem with that
version of PGP. Can you try a more recent version?

Not a bug report. Suggest asking on gnupg-users@gnupg.org
mailing list.

1.4 no longer allows making signatures with expired keys

Added feature for 1.4

Fixed for next release.

GnuPG is not a VPN product

Fixed in 1.2.6

Fixed in 1.2.6

Fixed in 1.2.6

User error.

Closing as unreproducible.

This seems to have been resolved (all participants went quiet)

Use the --allow-freeform-uid option when generating the user
ID. That allows you to use any characters you like.

In the *host* portion? Can you give an example?

This doesn't make any sense. GnuPG does a byte-for-byte
comparison of user IDs before merging them. It certainly
does not play capitalization games.

This was already fixed for the upcoming 1.2.5 release.

Done

Fixed, thanks for the report! Patch is attached.

I never intended multiple comments to be in any particular
order, but it's easy enough to maintain the order given.
This will be in the next devel release.

Oh, for crying out loud. I forgot to remove a piece of
debug code. Here's a patch.

Fixed for 1.2.5.

This is a known problem with Bzip2 1.0. Either upgrade to
Bzip 1.0.2, build with --without-bzip2, or add a #include
<stdio.h> to the top of g10/compress-bz2.c.

Fixed for 1.2.5.

This bug was fixed in 1.2.2.

Already fixed for 1.2.4.

The code part of this has been handled. It is up to the
translators to do the rest. I'm marking this as suspended
(since it is not really closed).

Done.

Not a GnuPG bug

Done.

Not a bug.

Didn't hear back. Assuming issue resolved in 1.2.3.

It seems to be there. gnupg/tools/lspgpot.

Done.

GnuPG 1.0.7 and later have --refresh-keys.

Already fixed :)

That's a feature. Since anyone can add a user ID to any key
(even if they do not have the secret key), requiring a
self-signature ensures that the key owner approves of the
additional user ID. You can override this protection by
using --expert.

This is not a GnuPG bug. This is a keyserver bug: many
keyservers do not handle more than one subkey. Use
"subkeys.pgp.net" as your keyserver to reach a working
keyserver.

Fixed. Thanks for the report!

GnuPG does not let you merge secret keys - if you want to
import a new secret subkey onto an existing secret key, you
must delete the existing secret key first.

The buffering oddity you are seeing with "tee" is because
tee doesn't finish pocessing until the input file is closed.
That's a "tee" thing, not a GnuPG thing.

Please try the 1.2.3 release candidate at
ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.2.3rc1.tar.gz

Photo IDs not appearing in the --with-colons listing is a
feature, not a bug. The assumption is that when in
--with-colons mode, GnuPG is being called from an external
program and to cause a viewer to execute (and possibly pop
up a window) violates that intent.

Fixed.

Closing.