Lowered priority because in reality it is not possible to get a certificate for an arbitrary SigG key on the card. Only accredited CAs may issue certs and they want to keep full control over the key generation.

We discussed this, the proper solution will be for gpgtar to accept unicode arguments on windows.

Filtering by tags does now work in the certificate selection dialog even if the tags are not displayed. One needs to show the Tags column to display the tags.

Kleopatra now offers the creation of OpenPGP keys and CSRs for existing keys on

• OpenPGP cards
• PIV cards
• NetKey cards

As discussed, generating a CSR for a SigG key (used for qualified signatures) makes no sense because no CA would sign such a certificate.

We are hoping to have at least a beta release soon with gcrypt 1.9 that we can put in a Gpg4win-4 beta.

This works with the message class changing. We still need to do it for OpenPGP, too.

The problem is not with creation, that works. The problem is also not with files contained in the archive, they also work. The problem is the archive name. And that also seems to be correct in the way gpgtar extracts it as gpgtar successfully extracts the archive, but the created folder name has the broken character.

I think the main work of listed translation update has been completed, and other minor problems will be corrected in the future patch.

I can't replicate this on the command line. Anyway option -T is only valid with --create. Further the archive format is specified to carry utf8 filenames; thus --utf8-strings won't have an effect on --extract. Are you sure that Kleopatra runs

gpgtar --create --utf-strings -T -

and you pass utf-8 encoded filenames on stdin?

This has been resolved with rOb05416e7bc41

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