I've re-run the 'basic' self test several time, and it works every time (except
for the hmac problem).

I'm relatively certain that it is correct. I created by running 'make dist' on
my machine and transferring the entire libgcrypt-*.tar.gz archive to the Solaris
system and building libgpg-error and the libgcrypt archive there. The system
doesn't have libgpg-error or libgcrypt installed before. The only way I see
them being wrong would be if there is a gdb/gcc problem, which isn't completely
unlikely, the tools on that platform are fairly old (gcc 3.4.4).

Are you sure that the backtrace is really from svn1350? The given line numbers
don't match.

Trivial patch. Closing bug,.

I cannot reproduce this problem anymore. Neither with the test case
script, nor during ssh authentication with several card-reinsertions.

Moritz, this should be fixed in the current SVN of 2.0.10. Would you mind to
test it?

Another fix was needed, please use revision 1365.

It doesn't seem to work:

is the latest snapshot. I'd appreciate if you can test it so that I can close
this bug.

Note: It also works for gpgme_op_decrypt_verify, but the error code
GPG_ERR_NO_DATA needs to be ignored in this case. This is because we didn't get
a DECRYPTION_OKAY status message, and this is semantically the same as for a
signed but not decrypted file. We can consider making this case better in a
major upgrade when we change the ABI anyway, but not now.

Applied to trunk. Unfortunately it didn't made it into 1.1.7.

No response after 6 months. Assuming it is okay now.

Okay, I change the man page to read:

If you make a release candidate I can test it on a solaris machine.

That does not look at all like gpg.

Next time I do code staring I should put off my Joo Janta 200 Super-Chromatic
Bug Sensitive Sunglasses first.

Fixed in rev 4822

That was not a proper fix. We need to decode the hextstring in gpg-agent too.
Kiss Gabor figured that out.

Fixed in SVN for both versions (rev 4812). The batch generation will not be
fixed but I have documented that pitfall in doc/DETAILS.

Hi Werner,

The error message is gone. However, the search result sometimes includes
additional certificates, not just the ones the user searched for. These are
then also imported, at least when using kleopatra.

I received your mail today but I probably can't reply to
it before

Ludwigs test with 2.0.9 + patch shows that the error message does
not come anymore.
Werner, can you state when you did the change the dirmngr?
(E.g. what is the last released version that worked correclty here?)

D56: 167_gpgsm-ext-keylist.diff

--disable-padlock disables the asm code and thus you should not get the same
compile error. Please check that there is no

Tested with gnupg2 2.0.9-1 from Debian sid and python-pyme 0.7.0-4.

Right, older version of 0.10.x garbled the messages. We now take a copy of the
PR_BODY propery and work on it.

I confirm I can at least decrypt all my test mails
and see signed text.

OK, no crashes anymore.
Also, the only encrypted email works, but not the ones
with attachement or signed& encrypted.

Thanks; I tried that with exactly the same result.

use

Well it depends on what you send. If you start the message with an empty line
everything is fine. If not, it will not be shown because the MIME parser does
not find the body; it skips all header lines. I need to detect this situation
and restart the operation without employing the MIME parser on the plaintext
(which is needed for some message, though (IIRC, CryptoEx). It is all not that
easy because we work in streaming mode. I'll try to save the header lines and
employ a heuristic to detect whether this is a MIME message or plain text.

...some problems with svn 732:
I created testcases with gpg4win 1.1.3
(testcases_InlinePGP_withGpg4win1.1.3.pst sent by PM to werner)
and imported the pst file into outlook.
GpgOL doesn't show cleaned contents of the mails (without BEGIN ... END).
Decryption doesn't work.

great that you could find the problem! closing the report.

On Fri, Feb 15, 2008 at 10:01:15AM -0000, Werner Koch via BTS wrote:

Werner Koch <wk@gnupg.org> added the comment:

I am not sure about the problem but I updated getext which also updates the
iconv test macro. Can you please test this again:

ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.9-svn4694.tar.bz2
ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.9-svn4694.tar.bz2.sig

If this all does not help I guess I need to install an OpenBSD on my test box.

tested with gpgconf 2.0.8

I installed a new certificate which includes bugs.g10code.com.

Confirmed to work based on testing gpg4win 1.9.0 svn701.