- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 12 2021
Jan 11 2021
We are hoping to have at least a beta release soon with gcrypt 1.9 that we can put in a Gpg4win-4 beta.
Jan 8 2021
If you encounter this error message when running gpgconf --list-options gpg:
gpgconf: Option gpgconf-gpg.conf, needed by backend GnuPG, is not absolute
please simply create an empty file /etc/gnupg/gpg.conf or wherever your global configuration files are expected ("gpgconf --list-dirs sysconfdir" shows it). Bug fixed with commit rG9f37d3e6f307a9
Jan 7 2021
Jan 5 2021
Dec 21 2020
See T5192 for an updated release.
Dec 20 2020
In a discussion we decided that we need a deadline for GnuPG 2.3.0 so that we finally release it.
Dec 14 2020
Nov 23 2020
Released on 2020-11-18
Note that if you run into problems with a smartcard you should run "gpg --card-status" once. GUI frontends usually do that and this is the reason why this regression was not detected. Will be fixed in 2.2.25 (T5140).
Nov 18 2020
Nov 17 2020
A fix has been released; see T5052.
Nov 11 2020
3.1.12 was released on 2020-07-24.
Oct 28 2020
Unfortunately this new release has a regression affecting users with non-ascii account names. See T5098.
Oct 23 2020
Sep 4 2020
See
https://lists.wald.intevation.org/pipermail/gpg4win-announce/2020-September/000089.html
for the fixed Gpg4win 3.1.13
Sep 3 2020
Sep 2 2020
A bug was reported against this version which could happen also to older versions of GnuPG 2.2. In case of a crash please apply the patch over at rG8ec9573e57866dda5efb4677d4454161517484bc or wait for 2.2.23
Aug 31 2020
As a workaround please run
There seems to be a problem with Gnuk and thus Nitrokey tokens with 2.2.22. We are investigating this. See T5039.
Aug 27 2020
Aug 24 2020
Release done.
Aug 22 2020
Aug 20 2020
Jul 17 2020
Jul 16 2020
Jul 14 2020
It turns out that a test case in GPGME fails with that version. This is due to a regression I introduced in the passphrase repetition code for symmetric encryption. This will be fixed with the next GnuPG version; in the meantime you may use the patch F1646254.
Jul 9 2020
Duplicate - see T4702 instead