- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 16 2018
There is now an option in the debugging tab of the GpgOL config dialog to disable async decryption. This does not fully fix the issue but maybe mitigates it for some users that are very affected by this.
I decided today to install the beta version and give it a try, because the final version is not yet released. I still facing major problems, see attachment. The mail will not be delivered, but Outlook does not crash as before.
I finally got around to look at your examples. Sorry for the delay. I can reproduce the issue and understand the problem.
Done for libgcrypt, finally.
ntbtls adopts the way from the beginning.
Here are more links, which are basically Debian specific:
Oct 15 2018
I hope I did not choose inappropriate action in commenting here that I also would highly appreciate a cache timeout for OpenPGP Cards to reduce the exposure time of already unlocked card's keys. Would be great to get such an option
Just commited. Thanks.
The next version will have a details button to show the actual gpg output. This will often be helpful.
The current version is 0.9.10 and the reported 0.9.5 is 4 years old. We also received no more info.
The "Copy" menu item already copies public keys to the clipboard.
I now added a private key key copy option to the context menu.
Thanks for the report I'll look into it. Won't make it into the next release though as we are currently very close to the release.
It's implemented.
I could reproduce it at first, but when trying to make a screenshot clip
from that, I couldn't reproduce it any more, no matter what. It's either
gone (mail server update?) or needs a very specific sequence of events
that is quite unlikely.
This required some changes in the keyresolver / newkeyapprovaldialog in libkleo, too.
While I agree that it would be good for some useful comment to be generated, I'd currently settle for a way to manually set a comment on a key.
Oct 12 2018
@werner And perhaps it's worth mentioning that in my case it is gpg2 --version; gpg is 1.4.23. I have no idea whether that might play any role.
@werner Hi, the version output is as follows:
Thanks for the report. I would also like to see what
Oct 11 2018
Please check your ld.so (dynamic linker) setting (/etc/ld.so.conf and/or LD_LIBRARY_PATH).