Aug 3 2022
Aug 2 2022
Fixed in 2.2 and master. Did a couple of manual tests using 2.2 on Linux. gpgsplit comes handy to add a couple more tag-3 packets (same algos or one patched to camellia for the negative test)
This also points out that the cipher algos and modes of the symmetric encrypted session key packets where never checked for compliance. We only checked the compliance of the bulk encryption cipher algo.
This was added in b03fab09e188f7bb10237d4f20455e4026737e4e
Oh, there appears to be a reason for that. In line 699 of mainproc.c:
/* Symmetric encryption and asymmetric encryption voids compliance. */ && (c->symkeys != !!c->pkenc_list )
I have exactly this problem with yubikey here,
since i upgraded to gpg4win version 4.0.3 which contains gnupg 2.3.7 i get the same error as openpgp key not recognized.
The original issues have been addressed. Moreover, the actions are now available as buttons additionally to being available as context menu items.
@tigernero 2.3.8 is not yet released. Pretty sure gpg4win is a separate project, presumably you'll see a changelog entry here (as there is bumping to 2.3.7 in the latest 4.0.3) when it's in:
Aug 1 2022
The OpenPGP-related changes mentioned in T5832#161063 have been implemented.
I think this was mostly covered with T5362: Kleopatra: Add warning in compliance mode if gnupg version is not compliant and T5653: de-vs and GnuPG 2.3.3 error.
Has this been implemented?
As part of this the "Change Reset Code" button should be hidden in the general user interface.
I don't think that we need to fix things here. Important is that the WKD import uses a filter which imports only keys with the requested mail address. However, if a key with the same fingerprint already exists it will be merged.
The provided change does not look like fixing the problem for me. The path to gpgconf is still wrong and I am getting the same error both with master and with the patched tarballs:
make: Entering directory '/home/jjelen/devel/gnupg/tests/tpm2dtests' LC_ALL=C EXEEXT= PATH="../gpgscm:/home/jjelen/.local/bin:/home/jjelen/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin" abs_top_srcdir="/home/jjelen/devel/gnupg" objdir="/home/jjelen/devel/gnupg" TPMSERVER="" SWTPM="/bin/swtpm" SWTPM_IOCTL="/bin/swtpm_ioctl" GNUPG_BUILD_ROOT="/home/jjelen/devel/gnupg/tests" GPGSCM_PATH="/home/jjelen/devel/gnupg/tests/gpgscm" /home/jjelen/devel/gnupg/tests/gpgscm/gpgscm \ /home/jjelen/devel/gnupg/tests/tpm2dtests/run-tests.scm gpgscm: error running '/home/jjelen/devel/gnupg/tests/tools/gpgconf': probably not installed (wait-process "/home/jjelen/devel/gnupg/tests/tools/gpgconf" 2693795 #t): Configuration error
- Win32-OpenSSH support: T3883 in the branch gniibe/t3883, I think the initial implementation has been finished: meaning: working well for me, possible improvements will be:
- handling by threads (currently, each connection is handled sequentially, connection by connection)
- more uses by real users
- review for ACL
- currently, it uses NULL for sa, and allows only local connection by PIPE_REJECT_REMOTE_CLIENTS
- continue for experimental scute: T6002
- no use of direct SCD command, when possible but use gpgsm (to serve remote use cases)
- ECC support
- clean up
Jul 31 2022
Jul 30 2022
I can't find a url to download gnupg 2.3.8 for windows is it possible to know when gpg4win v.4.0.4 is out which fixes this bug? because currently on windows systems I am stuck using yubikey.
Jul 29 2022
It is unlikely that the tofu stuff will get into widespread use in the 2.2 version - if at all.
Fixed quite some time ago.