Please try using the current version (3.1.14) and if the problem persists re-open this bug. In this case we will also need a more detailed report.

(Reporter has problems running his own keyserver and accessing it.)

Please try gpg4win 3.1.14 and check whether your problem has gone.

Flagged as high becuase this is RC for Libgcrypt 1.9

rG6850f21d08b2: po: Fix Simplified Chinese Translation. is a fix for adjusting columns; The number means the number of columns.
rGf4a8be0950ea: po: Fix Simplified Chinese Translation. is a fix for:

• SETERROR is a command name of pinentry which should not be translated.
• The message is expected to be displayed in four lines.

Please check following translations:

"do not detach from the console"
"do not use the internal CCID driver"
"do not use a reader's pinpad"

Those are explanation for the options to instruct gpg-agent or scdaemon, not do something.
It's not a text to users.

Sorry, I didn't read your message above, and it's applied and pushed to master, due to exactly same reason (it's so big).
It's easier (at least for me), when it's in git repo.

I've attempted the fix a couple of times now, and it doesn't seem like Kleopatra is running with elevated privileges, but I'm still encountering the permission denial.

Thus better add a

&& !defined(__clang__)

Sure that the FreeBSD compiler does not define it? I am pretty sure it does.

According to list of attributes in the clang 12 documention, there is no such attribute in clang. However, the clang-11 compiler (as seen in Debian) does not define __GNUC__, so the proposed patch does not affect the status when building with clang.

I would prefer platform-specific code (i.e. the function win_get_user_name) to be put in separate .cpp files (e.g. newcertificatewizard_win.cpp). In fact, there should probably be helpers defaultFullName() and defaultEmailAddress() with platform-specific implementations, so that the using code doesn't need any #ifdef <platform>.

You may want to check that clang supports this attribute as well.

Build Result:

Hi there, this change is very useful on the Homebrew project's upcoming ARM port. The Mac package manager's base library prefix will change from the existing presumed defaults to prevent backwards-incompatibility, making pkg-config compatibility somewhat more important.

Actually this isn't really a special case when you want to migrate your existing ssh keys to gpg and import them. As stated in this guide https://opensource.com/article/19/4/gpg-subkeys-ssh-multiples, what you need to do currently is export the master key with its private keys, delete the imported ssh key from your keyring and then import your private keys again.

In T5214#140791, @werner wrote:

For directories this can't be done because not only the server reads the directories but also other deployment tools (e.g. rsync).

update for gnupg po/zh_CN.po
D518: po: Update Simplified Chinese translation po/zh_CN.po
the update is so big, so please review when you are free, and do not be push
thanks for all help

I fixed the latter two points. For directories this can't be done because not only the server reads the directories but also other deployment tools (e.g. rsync).

Reimplemented 8 block parallel in "vertical" orientation.

With little extra effort, stitched implementation turned out ok after all.

I removed gnupg from the %AppData% directory and restarted Kleopatra, but I am running into the same permissions issue.

I removed gnupg from the %AppData% directory and restarted Kleopatra, but I am running into the same permissions issue.

Hope he/she could help with that.

We should see that we can implement an auto-key-locate feature also in gpgsm. This would allow us to fetch the key as needed from the AD or another LDAP server.

please move away %AppData%\gnupg
it usually expands to c:\users\yourusername\AppData\Roaming\gnupg

Screenshots of the issue are attached.

Use released version or post to gnupg-devel for help.

Please report about released versions. If you have problems building from Git, posting to gnupg-devel is the best way forward,.

When building from git make sure that you have all tools installed and use
./autogen.sh --force
before running configure. Do not use autoreconf etc.