I can reproduce the issue and give it high priority. This is a curious problem of Outlook triggered by the improved send code in Gpg4win 3.1.3.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 6 2018
Here's the debug log file.
Thanks for your answer. So i think we must wait for the Update and downgrade to 3.1.2.
Da wir eine internationale Software sind bevorzugen wir in diesem Tracker Englisch. Ich hoffe das ist ok.
Thanks for the report. I was not aware of this but Indeed the fix should be easy. I think I already know the cause ;-)
Address book integration is in. What is still needed is to respect the overrides in the interactive key selection dialog.
I created gniibe/secmem branch for this.
https://dev.gnupg.org/source/libgpg-error/history/gniibe%252Fsecmem/
Sep 5 2018
well, i tried to push, anyway, but it looks like playfair is rejecting my pushes:
@werner -- yes, i am asking for a change that is specific to the way that gcrypt interacts with the Linux kernel. The minor patch i've proposed only affects a codeblock within #if defined(__linux__), so i don't believe it would have an effect on other Unices. I hope that people working with other kernels will propose any necessary fixes for them.
Thanks for the clarification.
Which is the correct way to handle this. We merely gave the MDC packet a standard packet structure so to help with debugging. Decryption needs to defer the 22 bytes to be able to detect the MDC packet.
Perhaps, the missing length information in compressed data packet is confusing. The length can be determined by the assumption of existence of 22-byte MDC packet.
Here is my understanding.
Sep 4 2018
I'm looking at my personal Inbox on both computers.
I received the encrypted mails, before I connected computer B with my Account
And yes, I'm using an exchange connection.
Thanks for the details. I tried to reproduce it but again for me it works. Still I give this high priority as this can be a blocker in deploying GpgOL and we should fix it for the next release.
I have additionally the problem, that signed and encrypted S/MIMI messages are handled by GPGOL even if S/MIME support is disabled.
Gpg4win-3.1.3 was released on 08.31.2018
The original reporter in the gpg4win-forums reports that this does not work reliably. :-/
Gpg4win-3.1.3 was released.
Gpg4win-3.1.3 was released.
Gpg4win-3.1.3 was released. This issue can be closed. Hurray!
Gpg4win-3.1.3 was released.
Gpg4win-3.1.3 was released.