$ gpgsm --help
gpgsm (GnuPG) 2.0.11
[…]

--assume-binary              předpokládat vstup v binárním formátu

-r, --recipient ID_UŽIVATELE šifrovat pro ID_UŽIVATELE

--prefer-system-dirmngr      použít systémový dirmngr, je-li dostupný

Commited to all branches. Thanks.

The patch fixes the segmentation fault:

Please try this patch.

It is easier to allow them than to deprecate them. Frankly there is still some
code which handles the - despit ewhat I wrote to the ML.

ok, please enable s/mime support by default for next release.

Can you give some examples? In GnuPG we fixed that at some places.

See T1137

Duplicate of T1137

It can't do that for technical reasons. We should enable S/MIME support by default.

We can implement that in 2.1 after having replaced the current keyring based DB
with the Keybox based one. The latter is far more efficient and does not
require sequential scans all the time. Some breakage will anyway happen and
thus a new selection strategy, i.e. a well defined one, won't harm either.

Yes, the whole X.509 PKI busieness is a mess. However You are right that
Dirmngr should not replace a good by a broken CRL. As you can see in the code
there is a little race condition which usually has no bad effects but might come
into the game here. I have not looked at the code for weeks, though. I'd be
glad to receive a fix.

Yes, this looks very familiar to me, although I thought the problem only occurs
if I both sign and encrypt the message.
I can't remember GpgOL's S/MIME support setting; and I'm unable to verify,
because I uninstalled it in the meantime (switched from OpenPGP to S/MIME
solution). You can mark #1130 a duplicate of #1137 if you like (though mine was
created 10 days earlier).

sorry, jroemmler, I have mixed the issue numbers.
Again: I think your issue is the same problem like T1137 (GpgOL could not
decrypt/verify messages in "sent items" folder if sime support is disabled).
Can you confirm it?

Nope, I'm using MS Outlook 2003 and #1110 crashes in Outlook 2007, whereas his
Outlook 2003 seems to work fine for him.
BTW: My Outlook 2003 doesn't crash, it just shows garbled content in the message
body (but that may be by luck).

Seems to be the same issue like T1110, right?

Just for completeness, there have been more fixed in dirmngr
and the symptom seems to also have happened because an http proxy
behaved
strangely.http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/trunk/src/crlfetch.c?root=Dirmngr&rev=323&r1=320&r2=323

I read RFC 3280 and I thing I understand it.

Sorry, I added gpgsm output without LDAP attempt because valid up-to-date CRL
for one CA was cached already. Follows output demonstrating stop on LDAP failure:

I got the idea probably. The structure of DP extension assumed by dirmngr is:

I did some debugging and I found that problem is not that it does not give up on
first successfully fetched CRL regardless expiration time. The real problem is
it simply fetches from all DPs and it rewrites the CRL with CRL from next DP on
each iteration.

Still the same problem with Gpg4win 2.0.1-rc1.

Any news for this issue ?

Werner needs to try something to make sending MIME emails with Exchange
for the first time.
(So this problem will still be in 2.0.1rc1.)

Asg, could you test 2.0.1rc1?

D109: 254_gpa_desktop.diff

D107: 253_typo_adresses.diff

Sorry, didn't mean to change status with previous message, just confirming that
the issue I raised is resolved. Will try to set it back now.

These changes fix the problem as reported (retested gpg versions 1.4.10 and
2.0.13-svn5147). Thank you!

There is further an "it's" which must be "its". Patch attached.

D108: 252_its_typo.diff

D103: 251_gnupg_2_spell.diff

Patch for 2.

D104: 250_gnupg_2_spell.diff

Patch for 1.4.

D105: 249_gnupg_1_4_spell.diff

I just installed 1.4.10b, and see that you added bzip2 support back in. Thank you.