This was fixed with 7eed3c4c5e9f84bed0e412213cf404a18cd54358
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 27 2018
Oops. I also opened T3939 about this.
I can't reproduce this with GnuPG 2.2.6 or 2.2.7 beta and GPGME 1.11.0 . There I correctly get User Canceled for OpenPGP but "No Secret Key" for S/MIME, also using GpgME++.
Hi Carlos,
yes sorry, but due to a design limitation it's impossible to move mails while the decrypted / verified content is visible. Our task for this is T3459 (so I'm closing here as invalid even though the problem is valid.)
Apr 26 2018
Apr 25 2018
T2984 might also be related as the fetches are ldap.
Still happens. There are also "BER" errors that seem random.
Thanks for your report!
Apr 24 2018
Very strange behavior caused this. Outlook seems to detach from an object model call, handle a window message, and then return the object model call.
Apr 23 2018
Do you have an example for this in our code?
Apr 20 2018
I (as the maintainer of pinentry-qt) fully agree with your sentiment. I changed it in pinentry-qt (since version 1.0.0) so that the keyboard input is only grabbed (which is a security feature) when the input focus is on the passphrase entry as I found it very annoying myself.
This task and Forum reports about CRL errors caused me to investigate a bit and we found a Bug with CRL's on Windows. T3923 which might be the root cause.
Looks ok now in my tests. I still want to test against more CA's with more CLRs (e.g. COMODO and CACert)
Was Okish in my last tests. But I did not fix anything compared to 3.1.0
The commit mentioned fixes the problem.
Thank you very much. It helped. I can reproduce the problem now.
"Invalid crypto engine" Means that there is some internal error in the signature verification / decryption.
I got an Idea how to improve the situation here. But its very complex and might break Outlook even for unencrypted mails. So it's very invasive.