Gpg4win-3.1.3 was released.

Gpg4win-3.1.3 was released.

Gpg4win-3.1.3 was released.

Gpg4win-3.1.3 was released. And the original reporter confirmed the fix.

Gpg4win-3.1.3 was released.

Closing.

Gpg4win-3.1.3 was released.

Initial development finished.
Now, my plan is:

• a bit more tweaks for gpg-error-config-old to support new ways (such as --variable=*)
• testing on *BSD
• not including gpg-error-config-new to next libgpg-error 1.33
  • Now, gpg-error-config-old has forward compatibility, so, no problem
  • Possibly include new gpg-error.m4???
• After 1.33, merge the branch (not directly by "merge" but merging all changes with relevant commit logs) to master of libgpg-error. This means:
  • gpg-error-config-new
  • checking difference between old and new at build-time
  • "make check" tests difference between gpg-error-config(-new) and pkg-config (if available)
• 1.34 1.33 will have all new features
• Then, we will migrate other software of our GnuPG
  • libassuan
  • libgcrypt
  • libksba
  • libnpth
  • ntbtls
  • gpgme

Gpg4win-3.1.3 was released.

Gpg4win-3.1.3 was released.

Gpg4win-3.1.3 was released

Gpg4win-3.1.3 was released.

Gpg4win-3.1.3 was released.

By grabbing I guess you mean that the cursor / keyboard input is automatically focused on the input field? I also noticed that this sometimes does not work well.

I can see MDC packet of 22-byte (which starts by 0xd3 0x14, and then 20-byte SHA-1 hash), when SEIP data packet is decrypted.
I don't see your situation.
How about with no compression (-z 0)? I mean, compression is not applied to MDC packet.

Assuming dirmngr is just connecting to localhost on one of the following ports: 9050, 9150 or 8118 (maybe) then an interim workaround could be achieved with ncat (or netcat, or nc ... but ncat is like those two on steroids and will happily pass a shell exec function to connect to the remote host with openssl too (which may be preferred depending on the size of the LAN).

The implementation by Bourne shell is not perfect. Parsing .pc file depends on glob pattern match, which would have unexpected behavior in some cases (e.g. when .pc has no variable definitions and it only has "Requires: somepackage >= 1.0", the line matches glob pattern of "*=*" which looks like variable definition).

By rEfb1d0cd7105e: Support module dependency., it supports version dependency handling.
While it's far from pkg-config replacement, I think that we can use the script for all GnuPG software with *.pc file.
I mean, this single script for all.

Today, I wrote a script:

BTW: For TSA keys an additional key (usage) flag ("This key may be used for time-stamping") in RFC 4880bis would be nice. What do you think?

https://www.gpg4win.org/version3.1.3.html < beta28 has the fix. If nothing untoward happens this will be the final version to be released tomorrow.

Release done with these major news:

• gpg: Refresh expired keys originating from the WKD. [T2917]
• gpg: Use a 256 KiB limit for a WKD imported key.
• gpg: New option --known-notation. [T4060]
• scd: Add support for the Trustica Cryptoucan reader.
• agent: Speed up starting during on-demand launching. [T3490]
• dirmngr: Validate SRV records in WKD queries.

I have to revert the changes. The problem is that with attachments included Outlook must parse the S/MIME Mail. The code I've added to handle the PGP/Inline in GpgOL would result in hidden attachments as Outlook no longer properly parses the S/MIME Mail, we only decrypt the body and so attachments are gone.

I can't reproduce it. I don't get the Properties have changed dialog.

Problems here are:

• The icon theme needs a build tool to generate which is a problem with CMake Crosscompiling.
• Building natively and then packaging the icontheme.rcc would work
  • The breeze-icons.rcc must be renamed to icontheme.rcc and copied to <instdir>\bin\data
  • index.theme must be in the same place.
• The GpgOLGui would not find icons from that because it would need to link to kicontheme.
• The Kleopatra icon in breeze would need to be patched out as we want to use the old icon for kleopatra.

We have debug output now to show which commands are running.

We have a progress dialog now and only show details on request. I've also fixed a bug that you could trigger learning the keys twice which lead to undefined behavior.