3.1.6 is released.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 27 2019
3.1.6 is released. Please test again and reopen this issue if you still have problems.
Thanks!
3.1.6 is released
3.1.6 is released.
3.1.6 is released.
3.1.6 is released.
3.1.6 is released.
gpg4win 3.1.6 is released which contains this fix.
3.1.6 is released please use that one.
3.1.6 is released
Sorry, this did not make it into 3.1.6. But I'll definitely see about it for the next release. If it is an institutional / corporate issue you could also contract us through www.gnupg.com
I don't think this is a bug. Failure to encrypt when CRL check fails is expected.
Mar 26 2019
I changed it. My rationale to check for <=0 here was to catch "-1" invalid handle values that might be somehow created / passed and not caught earlier.
Trying to install the update manually (according to windows update my windows is fully updated) it says "This update is not meant for your computer" and aborts.
This has been implemented.
I've started some documentation how to repair a broken archive under: https://wiki.gnupg.org/TroubleShooting#Restoring_corrupted_Archives_created_by_Kleopatra
If the filename embedded in the encrypted message differs from the filename Kleopatra uses (which is derived from the file system filename) Kleopatra will now show the filename. This should cover the case where users receive an "Attachment.pgp" and do not know what that is.
Could it be that you are running into: T4347 ? Maybe this will just be fixed for you then in the next version.
Hi,
I'm pretty sure that I finally understood it and fixed it. There was a data mismatch between the IMAPISecureMessage and IMAPIMessage which somehow only happened for sent mails. This case is now handled.