Thank you!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 18 2024
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 :
MLKEM768 :
Mar 17 2024
Mar 16 2024
Mar 15 2024
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.
Mar 14 2024
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,
Mar 13 2024
Hello Werner,
the above is an excerpt from the exim log, I do not think the full bounce is more enlightening, vsrv21575.customer.vlinux.de got 550 from ellsberg.gnupg.com after " MAIL FROM:<ametzler@bebt.de>":