Employees of g10 Code and close friends
Details
Jan 17 2022
Dec 7 2021
Dec 3 2021
Dec 1 2021
The default validity period can be specified in the configuration file with
[CertificateCreationWizard] ValidityPeriodInDays=42
Nov 30 2021
Quick gen key is only used for the keygen in GpgOL and KMail. Kleopatra itself uses the old batch generate interface.
--quick-gen-key supports this but there is no general option; the 2 years are hard coded.
Jul 1 2021
Jan 11 2021
This works with the message class changing. We still need to do it for OpenPGP, too.
Jan 8 2021
This has been resolved with rOb05416e7bc41
Jan 3 2021
Dec 21 2020
Dec 4 2020
And I also did a backport to 2.2 :-) See rGa028f24136a062f55408a5fec84c6d31201b2143
Nov 11 2020
Jul 28 2020
May 29 2020
May 19 2020
Mar 12 2020
There are likely some bugs in the new code and I also want to do some improvements; see rGb4f1159a5bd7. But things should basically work as before and thus I set this again to testing
Feb 28 2020
i'd be unlikely to ship anything as /etc/gnupg/gpg.conf or /etc/gnupg/dirmngr.conf just because of the mess that admins have to deal with when shipped config files change.
Arggh, gpgconf uses its own option parser so adding the global config file there will require some extra work.
@dkg You might find this interesting. Debian could do stuff in /etc/gnupg/gpg.conf or /etc/gnupg/dirmngr.conf without patching GnuPG to change some defaults.
Feb 27 2020
All done in master with the latest libgpg-error (see T4859). There is always a global configure file in /etc/gnupg (or whatever "gpgconf --list-dirs sysconfdir" prints). The name of the configure file is the same as the user config file (gpg.conf, gpgsm.conf, gpg-agent.conf, ...) but for gpg.conf no versioned config names are used.
Feb 21 2020
Okay, we now have global conf files in master. The extra flags to ignore or force certain options will be added to libgpg-error.
Feb 4 2020
Jan 16 2020
Dec 20 2019
This is fixed now.
Dec 19 2019
This is fixed in Gpg4win-3.1.11
Dec 18 2019
Dec 16 2019
We now have a decent error message for this.
Nov 1 2019
Maybe it is the same issue described in https://dev.gnupg.org/T4717 ?
Oct 31 2019
Oct 28 2019
I think we can fix it by removing the smime attachment from OOM, because we still have it in MAPI, we just never cared that it was also in OOM (where only our decrypted attachments belong) because it was hidden.