I'm not 100% certain but I think that it is likely that your problem is fixed with the upcoming 3.1 version. We have reworked how GpgOL encrypts there a bit ( T3509 )
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 21 2018
Mar 20 2018
The field is now renamed to "Activate GnuPG Profile" to make it more clear the the button activates a new profile.
I've added this to libkleo formatting now. But seeing it and thinking more about it I don't like it. As I think that the export is mostly for "You give this to others" information about the subkeys is too verbose. The current header should suffice as "some info for differentiating between keys".
Kleopatra now shows this:
This works now reliably in my tests.
Cancel is now handled and the key is not removed if the user canceled.
I got beta feedback which after analysis showed that parts of the encrypt changes in 3.1 that would have addressed this lead to crashes. So we had to disable it for now and block Outlook again as temporary blocking is better then "random" crashing :-((
Mar 19 2018
Reproduced again with a brand new Yubikey 4 Nano on another Arch Linux machine with a newly created test keychain:
Mar 18 2018
I experienced this issue today while cleaning up my keychain. I recently switched from pgp to tofu+pgp trustmodel and this caused me the above error when doing:
Mar 17 2018
Mar 16 2018
With the tab layout I think that this is resolved.
fyi, I pointed folks at https://github.com/keybase/keybase-issues/issues/1712#issuecomment-372158682 to this issue
For factory-reset, rG2c85e202bc30: scd: Better user interaction for factory-reset. fixed the issue.
Mar 15 2018
I give this high priority as I would love to have this fixed for the next release.