However, if I turn the reading area/preview are on, anything works fine :/

Hi,

thanks for your message. I installed the gpg4win beta 194 (3.0.0, released at
15th November), however, Outlook now crashes with another error message:
Runtime Error!

Program: C:\Program Files\Microsoft Office\root\Offie16\OUTLOOK.EXE

This application has requested the Runtime to terminate it in an unusual way.
Please contact the acpplication's support team for more information.

The error message occurs, when I _select_ an encrypted/signed message in outlook
(preview window is off, so the message should probably not be loaded, yet). I
can't open the message itself (but I'll need to enter my private key pin).

Is this related to this bug or should I open a new one?

Best,
Florian

I've just announced a new 3.0 beta that contains the updated GpgOL

http://lists.wald.intevation.org/pipermail/gpg4win-devel/2016-November/001659.html

Please let me know if it still crashes for you with that version.

Thanks a lot. I will test as soon as you release the test build.

Hi,

Thanks for testing gpg4win This issue was already reported in T2335 and has
been resolved (but not yet released).

I'll upload a new beta next week.

Regards,
Andre

gpgol 2.0 won't change the messages on the server anymore there might be code
paths leading to that under error conditions but i'm not aware of any. And the
fallback is first to try to revert them.

Still true for sending but for sending we don't have a choice. But decryption is
now done in a different thread.

I've tried this again with the current development version after a very large
refactoring how we handle mails. The bug appears to be gone. I've tested 10
times to send a file with closed / open outlook and with and without encryption
active.

If I install gpg4win-2.3.3 on the same system / setup the crash is reliably
reproducible.

It's still likely that we made a reference counting error internally in code
that was changed / fixed now. And Outlook released the Mail object too early and
crashed.

Kaspersky probably had some similar error in their code.

I'll upload a new Gpg4win beta with the new gpgol next. I'll ping in this issue
once thats done so you could ideally confirm that its fixed now.

That's awesome aheinecke! Honestly wasn't sure if this issue would ever get much
attention. Thanks for the effort in making Gpg4win a more secure product!

Duplicate of T2341

Thanks for your report,

This was already fixed in T2341

Which is currently not yet released. I'm marking this issue here as released
with superseder (duplicate) to keep the tracker clean.

GpgOL is built with DEP and and ASLR now. Need to enable this for GpgEX and some
other parts of Gpg4win, too. So not yet fully resolved but I keep it in mind.

Fixed with: 5579c4b4f

The code was overcomplicated as it was based on a bad assumption about Outlook
which I never questioned myself. We now properly encrypt in the send event so no
need for ticklish threads / callbacks.

Fixed for the next version with 037a5a7ed

Interesting...

The Kaspersky issue is about Outlook 2007... Is that supposed bug really already
THAT old?!

This could be a nasty one. The crash occurs after the data structure of the mail
was unloaded in outlook and GpgOL already completely detached it's event
handlers from the object and frees up the memory. GpgOL is not executing any
code when the crash occurs. That outlook blames GpgOL is likely because it jumps
into an invalid memory region that was allocated for GpgOL but is no longer
valid. This shouldn't happen though as we have already successfully unregistered
all our callbacks.

So I currently think that somehow when using send from explorer outlook through
some side effect / bug does a callback into GpgOL's event handling code which
was already destroyed. I'll try to confirm that theory on monday by keeping the
event handlers around after the unload event occurred.

Also does not appear that we are the first ones with that problem:
https://forum.kaspersky.com/index.php?showtopic=225375

:-/

Thanks! :-)

Thanks for the report. I am able to reproduce the problem.

Looking into it.

To make it clear: I'm not even trying to sign or encrypt, just send a plaintext
message with attachment also in the clear.

Hi,

There was a problem in Gpg4win-2.3.1 that GpgOL and GpgEX might be unable to
start Kleopatra or GPA. This problem has been fixed with 2.3.2

Thanks for your report. Please check if 2.3.2 does not solve your problem and
let us know if it still persists.

Regards,
Andre

Gpg4win 2.3.1 and 2.3.2 included 64 bit versions of gpgol.

Hi,
Thanks for your report. Could you please retest with 2.3.2 we've fixed an issue
where GpgOL had problems communicating with Kleopatra that could cause your
behavior although I'm not 100% sure as I can't reproduce your problem.

Thanks,
Andre

Thanks for your report. Sorry I missed this for 2.3.2.
I'll look into it for the next version.

Hi,

Thanks for your report. With gpg4win-2.3.2 we addressed that problem. See also
issue2319 which was also about this problem.

Please let us know if you still have that problem with 2.3.2 I could reproduce
it in testing and with the fix it no longer happens so I'm hopeful this can be
resolved :-)

Regards,
Andre

Duplicate of T2319

With 2.3.2 the fix was released.

With 2.3.2 we've fixed another bug that sent mails were still handled by gpgol
even when s/mime was disabled.

So far I know of no other problems -> Resolved.

Fix commited to master with rev 643575f

Duplicate of T2171

You can now. Thus is not a bug but a feature request.

Note that we do not use Microsoft compilers but use gcc and in cross build
environment.

Just as a note, this bug is for the "MIME Aware" interface with event driven
sign / encrypt.

Actually we are working on a 64 bit version.

GpgOL-1.4 which we will include in 2.3.1 will have an option dialog where you
can enable and disable S/MIME. Default in 1.4 is off.

-> Testing until 2.3.1 is released.