Will go into 2.2.6
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Feb 22 2018
It makes --export-secret-key-p12 the recommended way to transport a privat CMS key. (fine, if this is, what was intended).
(Note that there is a typo in line 259).
I just tested version 2.0.7-beta8 x64 and I can confirm the bug is fixed, GpgOL can decrypt messages properly. Messages also appear to be properly signed.
No more info received - assuming this has been fixed after 1.2.20
Will go into 2.2.5
I changed the wording to suggest the use of proper transport security.
Thank you. With that message I could reproduce the problem and have a fix. I now get to decryption failed / no secret key as it should be.
Feb 21 2018
hm, i think this is the file:
You can find the message attached.
Message has been saved from Outlook 2013.
Thanks for your report and analysis.
Feb 20 2018
Thanks for tracking this down. I'll fix.
Bissecting between gnupg-2.3-base and master pinpointed commit ecbbafb88d920e713439b6b1b8e1b41a6f8d0e38 as the origin of the bug. This commit changed MAX_FINGERPRINT_LEN from 20 to 32, but the get_user_id_byfpr function in g10/getkey.c still assumes the old value.
Feb 19 2018
Note that there is no standard for this. In particular the encoding of filenames with special characters are different in almost all implementations. I tried to find a common ground for our implementation.
Just to be clear I think this issue is valid and we should add more checksum tools in the future. But I would want them to use libgcrypt and confirm to the standard *sum command line arguments like -c.
On saturday I could observe the problem with a fresh Windows 10 Home edition.
The problem seems to have to do with the locking of the TOFU database.
Feb 18 2018
Feb 17 2018
Feb 16 2018
This handles the problem, thanks.
Kleopatra can still be used without UI Server connectivity. But this might point to a bigger issue.
Hi Werner,
This is a MUA thing. Do you ask whether we plan to add it to GpgOL?
See T3796
Sorry, we won't do this any time soon. We may even shut the Bitcoin thing down. I was too troublesome from a bookkeeping POV.
My first GUI Idea does not work. From the Ribbon I don't see a way to find the currently used account. I could only look at all accounts that are configured and check the WKS publishing state for all of them.