Reading / marking old signed Mails, i.e. those signed with GPG4win 3.1.4, crashes Outlook 2013 with Exchange-Server. Error-log attached.
Description
Description
Details
Details
- Version
- GPG4win 3.1.5
Revisions and Commits
Revisions and Commits
| rO GpgOL | |||
| rOe8c7a5285420 Initalize pointer in mapi_get_header | |||
| rOe6e29900ce0e Check for error in dbg decrated oom funcs | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | aheinecke | T4262 Reading / marking old signed Mails crashes Outlook | ||
| Resolved | aheinecke | T4264 Gpg4win 3.1.6 | ||
| Resolved | • werner | T4289 GnuPG 2.1.12 release |
Event Timeline
Comment Actions
While I can't reproduce it myself (because I probably don't have the right mails in my exchange) looking at your log I think that I see the problem there might be an issue with the error handling in openProperty. So for old mails the openProperty probably fails because we have exchange online for that and the property is not yet available in Outlook and then the error is not correctly handled and it crashes.
I don't think this crash is a new regression in 3.1.5, or is it for you? Does it also crash if you disable memory debugging? There is a Problem with the debug code there and your log shows a crash in the debug code.
I've uploaded a binary with this fixes:
https://files.gpg4win.org/Beta/gpgol/2.3.3-beta4/
Comment Actions
You are right that Outlook behaves normally if debugging is deactivated.
I had major problems with 3.1.4 and never used it until 3.1.5 came
along, so I guess it might be an existing problem.
Am 19.11.2018 um 15:46 schrieb aheinecke (Andre Heinecke):
aheinecke triaged this task as "High" priority.
aheinecke claimed this task.
aheinecke added a comment.While I can't reproduce it myself (because I probably don't have the
right mails in my exchange) looking at your log I think that I see the
problem there might be an issue with the error handling in openProperty.
So for old mails the openProperty probably fails because we have
exchange online for that and the property is not yet available in
Outlook and then the error is not correctly handled and it crashes.I don't think this crash is a new regression in 3.1.5, or is it for you?
Does it also crash if you disable memory debugging? There is a Problem
with the debug code there and your log shows a crash in the debug code.I've uploaded a binary with this fixes:
https://files.gpg4win.org/Beta/gpgol/2.3.3-beta4/*TASK DETAIL*
https://dev.gnupg.org/T4262*EMAIL PREFERENCES*
https://dev.gnupg.org/settings/panel/emailpreferences/*To: *aheinecke
*Cc: *aheinecke, JJworx, Rafixmod, ccharabaruk, gp_ast
This is an automated email from the GnuPG development hub. If you have
registered in the past at https://bugs.gnupg.org/ your account was
migrated automatically. You can visit https://dev.gnupg.org/ to set a
new password and update your email preferences.
Comment Actions
Ok. If you can confirm that then it means that my analysis is right. Still unexpected to get an error there. I have to do some more tests with Exchange Online but that would be another issue. If this issue is fixed by turning of debugging then it will also be fixed by my patches.