Interestingly enough, it's no longer the default in libcurl. We'll have to do
it for both the libcurl and emulation cases.

I think that if the primary key is expired, the subkeys should be treated as
expired as well. The only thing that makes the subkey valid in the first place
is the binding signature - which was issued by the expired primary key.

This is the occasionally-requested "--unwrap" command which would stop
processing after a single layer of the file. I.e. convert Enc(Sign(data)) to
Sign(data).

Fixed in svn rev 5021. Will be fixed for trunk as well. Patch attached.

D88: 224_bug1058-fix.diff

I looked at the code and it seems that you assume that a setuid(2)
changes more than just the UIDs of the current process. In particular,
you assume that environment variables change - that is not the case:
Like any envvar HOME does not change by calling setuid() or any other
system function. To change the envvars, your code needs to do this.

Does LDAP find these keys if they are C-style escaped? I guess that depends how
they have been put into the LDAP DB.

Ah, never mind. I found a key (ACCFFAE2) that nicely duplicates the problem.

Could you attach a copy of the public key you're having a problem with to this
bug? If you don't want to reveal that key for whatever reason, could you
generate another one with the 'é' character that shows the same problem?

I'm using Debian GNU/Linux 5.0 and most of the PGP Keys have been created with
Enigmail (the Mozilla Thunderbird extension).

Fixed in svn rev 5019 for gpg1 and gpg2.

What OS are you using? In general there is no need to use --charset; however
it is not related to the problem.

My fault, thanks. Fixed in rev 5016.

Thanks, that did it.

D87: 223_default-preference-list-change.diff

This is not a bug. For support please see http://gnupg.org/service.html .

Vendor is using Gnu Privacy Guard,which uses OpenPGP to encrypt the files and
we are at gpg (GnuPG) 1.2.6 version
We are receiving the error gpg: [don't know]: invalid packet (ctb=14) once in
a while.It doesnot happens for all the files.

Thanks for the report, I removed the dead entry. allow-pka-lookup was changed
into a verify option quite a while ago. Fixed in rev 5010:

Right, that was missing.

Is it possible to write out a message when we hit such a timeout?
Make that timeout configurable nontheless?

D86: 222_gpg-agent-sshttl.diff

The right way to delete an option is:

The options --batch or --no-tty will help you.

Outlook 2002 is not supported.

I find that on decrypting a encrypted message received using Microsoft Outlook
2002 (10.6838.6845) SP3, the decrypted message text is displayed in the From:
field area instead of in the body of the message.

Forget the second part. It prints this message only, if it indeed needs input
and giving --yes works in this case too. So there was a fault on my side.

Maybe we misunderstood(?). The gpg-agent is not used.

I don't want to decided whether thisis a bug. The thing is that using gpg with
gpg-agent is more of a temporary solution than something we want to work as
clean as possible. For such use cases it is better to use gpg2.

Don't put too much weight into gpg's exit codes ;-)

I need to check the first case.

Fixed in svn rev 5005. (gpg1 and gpg2)

It is basically the same code as used in gpg2. On a GNU system tty_get_ttyname
always returns "/dev/tty". This is used as a fallback solution so that we can
tell gpg-agent at least one tty which may work.

Since svn rev 5003, the warning is only printed if option --verbose is used.
That may be helpful for some users and does not complicate things too much.