Just a quick comment regarding GitHub: This mirror of the gpg repo hasn't been updated since many months. Please get the sources of gpg directly from the original source: git://git.gnupg.org/gnupg.git. See https://gnupg.org/download/git.html

The configuration pages can be hidden by setting the following config entries to false in the [ConfigurationDialog] group in kleopatrarc:

• ShowAppearanceConfiguration,
• ShowCryptoOperationsConfiguration,
• ShowDirectoryServicesConfiguration,
• ShowGnuPGSystemConfiguration,
• ShowSMimeValidationConfiguration.

Not sure if we want a separate AppImage for gpg & Co. Setting priority to "Needs Triage".

Second issue is also fixed.

Here's a patch against b091a250d1411f9962385d1338c13481da2e0f9e.

I do not think that we should put any more support for FDs into gpgrt. The goal is to move entirely to the Win32 API.

Files added and changed.

The implementation is for Power 10 and above. The improvement is as follow for AES128,

PS, knowing little about it, I tend to look at builds scripts here https://github.com/msys2/MINGW-packages on how to do things.
eg https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-libgcrypt

Thank you, it successfully cross-compiles from latest git commit (not sure if it "runs", not tested it).

Part 1 was applied. Part 3, Part 4, and Part 7 are irrelevant now, because we now have rndgetentropy which doesn't use device.

PS, knowing little about it, I tend to look at builds scripts here https://github.com/msys2/MINGW-packages on how to do things.
eg https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-libgpg-error

Thank you !

I don't know how runtime (of mingw) is thread-safe, but if it is, it should work well.

Thanks for your report.

It was in the middle of merging jitterentropy. Please see T5692 (newer jitterentropy uses pthread by default, which was disabled now).

First issue is fixed.

Rating as High because this can be used for a DoS attack on individual users.

Actually, I have already implemented 1, 2, and 3. For now, I will disallow exporting multiple groups at the same time.

Following patch should prevent assembly files being built at all with --disable-asm:

Thanks for your report.

Fixed, with using normal memory for ->mem.

->mem is just used to measure the difference of memory access.

It found that newer jitterentropy uses larger mem (128KiB), while older uses 2KiB.