There are no log file but you can run the test by hand:

Most work last week went into customizable MSI installers. The idea is that a customer of our Software will be able to obtain an MSI package that directly includes his specific configuration. Esp. for S/MIME this is useful because trustlist.txt and available root CA's can be configured in deployment.

Last week:

• For v5key, push a patch (the first one, more will follow)
  • rGfa4a2bd7a1ba: kbx: Fix short KID and long KID handling for FPR32.
• Fix of building for Windows
  • T4994: Windows: assuan_sock_init or WSAStartup by main/_init_common_subsystem
• Fixes of minor things (possibly, to be backported to 2.2)
  • rG2a34a2afea5f: scd: Silence compiler warning.
  • rGda3a4c54a8ce: agent: Fix coercion for pinentry_pid handling.

Iyou look at the key on the command line (or with Kleopatra's certificate manager), for example by using "gpg --list-key foo@bar.com" or by applying the command "gpg --show-keys" on the pasted keyblock you get this:

I realized that it fails with GPG_ERR_INV_ID (with gpg master) when it's on smartcard.
It can't be decrypted if it's on smartcard, that's true, but more relevant error would be good for this case.

Something looks odd about the way I pasted that key in there. The last 4 characters are bold, and it is missing an = sign.

Patch backported to 2.2

Pushed modified patch to master and 2.2.

We have had this in the past but it led to subtle build and, worse, runtime problems. Thus the decision to provide architecture dependent files and have configure complain for wrong files. Right, you sometimes get false warnings for non-matching cpu-vendor-os strings but I consider this less severe than the old problem.

That patch fixes the build problem I got into today when trying to build 2.3 for windows. So 👍 from me and please commit the patch as it is already required when assuan and gpgrt config no longer emit ws2_32 in their pgk-config --libs line.

I just saw that there is related discussion and a patch for this in T4994 so I will close again here.

to give you any help I would need to know the exact error. I can only tell you that this is not a problem related to Gpg4win something else must be messy on your system. The Uninstaller of Gpg4win cleans up all registry keys that do not contain user config and all files should be removed unless some other process on the system interferes.

This change broke for me the compilation of GPGME which I fixed with: 52f930c1ed7eee6336a41598c90ef3605b7ed02b I found that fix there OK because GPGME explicitly uses ws2_32.

Linking $(NETLIB) is required when the executable uses WSAStartup.

Phabricator allows it again to upload patches. It's D507

In Kleopatra/src/dialogs/subkeyswidget.cpp there is already a context menu for subkeys.

Well, it is now defined. We use a CMS object containing an OpenPGP keyblock container. Right, there is no open standard for it but with OIDs you don't really need them. it is a bit of a hack but it works with the majority of deployed cards and the overhead is quite small.

Still an issue, just noticed that with the 3.1.12 release announcement, it really looks ugly.

These weeks

• Learning new technology + standardization (direct purpose is to update Gnuk)
  • AEAD
    • CAESAR: https://competitions.cr.yp.to/caesar-submissions.html
    • NIST lightweight crypto: https://csrc.nist.gov/Projects/lightweight-cryptography/round-2-candidates
    • Ascon implementation: https://github.com/ascon/ascon-c
    • SAEB and SAEAES: https://www.saeaes.net/
  • AES smaller
    • (software) AES Smaller Than S-Box: (I don't yet read) https://link.springer.com/chapter/10.1007/978-3-319-16363-5_4
    • (hardware) Smashing the Implementation Records of AES S-box: https://tches.iacr.org/index.php/TCHES/article/view/884/835
  • AES software implementations
    • Historically, DJB implementation: https://cr.yp.to/aes-speed.html
    • Then, "Fast Software AES Encryption": https://www.iacr.org/archive/fse2010/61470076/61470076.pdf
    • Paper: "All the AES You Need": https://ko.stoffelen.nl/papers/sac2016-aesarm.pdf
    • Impl: https://github.com/Ko-/aes-armcortexm (including non-table version and masked version)
  • Some papers about AES with blinding (masking with random values)
    • https://eprint.iacr.org/2004/149.pdf
    • https://link.springer.com/content/pdf/10.1007%2F978-3-540-72738-5_10.pdf

@wener But it uses undefined data structure of "certificate" DO, IIUC. My point is defining DOs for OpenPGP, so that host side can construct OpenPGP object from those DOs.

Item 2 and 3 have already been solved by allowing to store a minimal key.