Fixed with: https://commits.kde.org/libkleo/1318d2e13764e736d29c902500c21979e99eef9c
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
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.
Apr 19 2018
Ok I tested with Exquilla. I configured an Exchange account once through Thunderbirds built-in account (IMAP) and once with Exquilla
Hey, you want to get this into 1.11.1 I assume - Let's consider this a bug fix and not another API change.
I have a patch for this, but its not so good and we did not see a chance to get it upstream. For even medium sized mail accounts it already took to long as Enigmail (or better the Thunderbird Addon API) is prohibitively slow.
Thanks for the report.
I clarified the title a bit to include exchange / exquila.
Let's use the new issue as the problem is described completely there and it makes it more clear.
This was done.
Apr 18 2018
Mh, we can probably drop the GPGME part of this. In the longer term I'm hoping for the automatic refresh in dirmngr. So that refresh-keys would not be needed.
Apr 16 2018
A reason we did not touch it in the past is that Ideally we don't want users to have to mess with refresh keys but would rather have this done automatically in the background by dirmngr.
I wonder if CACert intentionally sabotages X509 / CMS.
Apr 13 2018
3.1.0 is released and this issue is to our knowledge fixed.
( Apart from the part that was moved out to T3895 )
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.