Now you can untar and run

Noteworthy changes in version 0.3.2 (2024-01-12)

The extra option --debug-allow-pin-logging was implemented with commit rGe43bd2a7a78.

Way to late for a change and also adding another algorithm (SIV) complicates things for no good purposes.

Tested this some time ago.

Better don't remove your entire ~/.gnupg - removing the *.lock files after gpgconf -K all is sufficient.

This either requires an updated libassuan which allows "INPUT FILE=foo" in addition to INPUT FD=n" or using custom handlers in for INPUT et al. in gpgsm. I'd prefer the former. Anoter option would be to open and close the file in ggpgme and pass the fd.

Already done with rG89c7eccba51554 which will be in the next VSD release.

This is due to the changed format of the VERSION file.

I applied a fix to gnupg which also solves the issue.

We did this on purpose once - For Windows ppl it is just weird to see forward slashes.

Double backslash quoting is the culprit. For WKD requests the GPGMe QT code makes sure that the dirmngr has been started. This is done by running gpgconf --homedir FOO --launch dirmngr. gpgconf returns the homedir with backslashes on Windows to be be nice to ppl who wonder when they notice (legal) forward slashes on Windowns. Now when the spawn function along with its helper is called, it needs to quote the backslashes. But somewhere on the way back one de-quoting is missing and thus gpg sees double backslashes. That is in general not a problem but when checking whether this is the standard home directory, this does not match and gpg puts the socket into a subdirectory. In turn another dirmngr is started for the WKD purpose.

Yeah we should do an ntbtls release. As a core library it does no matter much which workboard we use. Let's remove it the vsd tag.

It does not matter how many gpgsm instances try to start a daemon. The same code is used for starting and this code first takes a lock. When using gpgconf --launch the same code is used too (indirect by calling gpg-connect-agent NOP /bye wityh options for the respective daemon).

I sued the done column because we have not assigned it to any milestone.

Fixed a long time ago.

We can't test this but assume that the fix for T6752 is sufficient here.

With rG239c1fdc28dcd0dc7aa5341be7c966da2231642a we now have a socketdir keyword for gpgconf.ctl. man gpgconf and look for that file. Will be released with 2.4.4.

gpg 2.4 now returns ERROR status lines for failed --quick-add-subkey and --quick-add-adsk.

Note that we now have also an option instead of the workaround from 2015

This seemed to be related to T6831 but here we have the case of different keys and not just different subkeys.

I applied your patch and also fixed another possible problem.