- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 11 2021
New option --force-sign-key for 2.2.28 and 2.3. Also added support to gpgme.
Mar 10 2021
Yes. I know that this is annyoing but I don't think we have a quick command for something like that yet. So editinteractor it is :-/
Mar 9 2021
Pushed to master with two commits:
This needs support for setting a certification expiration for gpgme_op_edit (maybe similar to the support for setting signature notations).
Looks okay. Thanks.
Actually we considerto remove this feature from the GUI because with the global config we have a more versatile feature now.
Note: If you want to set this early in your program you need to make sure that there is only one thread running.
Mar 8 2021
We have used this task for more than the usual release info, thus the new title. We will use
T5343 for the 2.3.0 release info.
and item 6. Now for more testing.
Except for T5341: gpgconf does not list default_pubkey_algo pseudo option anymore, this should be done.
Mar 7 2021
Maybe have gpg-wks-client(or also --export-filter) print a warning if the filtered result has a key expiration different than the original key? That seems the simplest way tp approach the problem.
Following @turkja 's advice, here's a python script I wrote that does exactly that:
I posted patch-set to mailing-list. Please check if AUTHORS/LICENSES updates are ok.
https://lists.gnupg.org/pipermail/gcrypt-devel/2021-March/005120.html
Can you please also update AUTHORS and LICENSE files? I would also ask you to add
Mar 6 2021
Fixed typos and applied to master. Thanks.
That is a problem on the macOS side, for example with their PINentry tool. Sorry, we can't help you here.
In any case we won't support a gpg4win version released nearly 4 years ago.
See the release notes for GnuPG 2.2.17 (T4606 first item). You need to import your peer's signature from a different source; e.g. ask them to send you your signed key by mail.
Mar 5 2021
Items 1 to 5 have now been resolved.
That it. Things works nicely for me. Won't be backported to 2.2 because this introduces minor changes in the behaviour.