What happens if you call gpgtar with --utf8-strings --cms additionally to the other options? And what happens if you pipe the archive to gpgtar's stdin?

The reset was due to running gpg-connect-agent reset /bye. I am currently testing something elese will get back as soon as I can turn back to 2.4

Let's wait a few days before we do a patch release. The missing CAPS lock indicator isn't mission critical.

New release due?

Thanks! Applied.

Note that this has also been ported to 2.4 and 2.2 and tested by looking at the status lines.

There are two locks here; (1) rw_lock for card_top (list of cards) access and (2) individual card lock.
It looks for me that:

• don't know how/what the thread 7208.2 does
• the thread 7208.3: KEYINFO, then PKSIGN (gets read lock for card_top, then, individual card lock)
• the thread 7208.4: SERIALNO --all (and wait for write lock for card_top)

Grr. That's why I'm only using #if DEFINE01 in Kleopatra so that undefined defines don't go unnoticed. (Update: And I just noticed that this doesn't actually work because, apparently, any undefined identifier is replace by 0 when evaluating conditional expressions.)

Thank you!

So, what is the state of this. Did a change already land in Kleopatra and how can we assure that all binaries have a W32INFO_PRODUCTNAME in their rc file?

See T7046 for the release info. Note that the mentioned fix for kwallet already landed.

Noteworthy changes in version 1.2.1 (2022-08-24)

Testing:

• Verify that T5359: Kleopatra: Loop in DeviceInfoWatcher with GnuPG 2.3 on Windows doesn't happen anymore.
• When you remove a smart card then Kleopatra should remove it from the smart card view.
• When you insert a smart card and then access it with gpg or gpg-card then Kleopatra should add the smart card to the smart card view.

AFAICS the bounce is correctly reported. You get the 550 at the mail from so that there won't be a need for several SPF checks if a sender wants to send to several recipients.

I extracted data from https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-pqc-02 and compose x25519 key and MLKEM768 key. Here they are.
x25519 :

We have discussed this yesterday. The idea/plan is to release the core library and the bindings as separate tarballs (created from the same repo) in the future.

Thanks for reporting this. Returning error codes to upper layers is not always easy because the original logic is that we have a global error counter to decide whether an operation succeeded. My fix to check the error code before emitting the DECRYPTION_OKAY status,