Tue, Sep 14
Mon, Sep 13
Sorry, GnuPG proper has no context menu or any graphic user interface. You need to install Gpg4win for this. Regarding use of gpg by other programs: There has been no change - other programs need to use the status-fd/command-fd interface and that has always been defined as UTF-8 and not as any native codepage. Please ask the makers of The Bat what is going wrong there.
Fri, Aug 27
Just for the record, Kleopatra and Gpg4win work totally fine for me on Windows-11 preview.
Thu, Aug 26
It is quite likeley that things don't work on a non-released Windows version. We have not tested with the released version but some of us already tried Windows-11 and the gog4win development versions do work. Please wait for the next Gpg4win version or an update of the Windows-11 preview.
Tue, Aug 24
Mon, Aug 23
So it is related to code page. Screenshots may be more informative:
Sat, Aug 21
Frankly, I don fully understand your report. Can you please clarify?
Note that with 2.2.8 we introduced full Unicode support on the command line. If you see scrambled output you may want to "chcp 65001" to get the output correctly rendered.
Aug 17 2021
I have done tests with 2.2 and no problems showed up.
Aug 3 2021
Jul 30 2021
Jul 15 2021
Forgot to mention one thing: after changing my user folder directory I lost all my Outlook contacts. I was able to recover them... make sure you have a backup before attempting this!
Jul 12 2021
I just had the same issue as hurui200320. My user name contains a "ç" and Kleopatra did not start. The Windows event logger reported a crash in libstdc++-6.dll. This was with gpg4win-3.1.16. Installing gnupg 2.3.1 did not change anything.
Jul 8 2021
Jul 6 2021
Jul 4 2021
Jul 2 2021
It is a matter of the used font. 2.2.29 will fix this problem.
Jul 1 2021
Same error message in Windows 8.1 x64 with the commands:
gpg --local-user 0x12345678 --sign-key 0xABCDEF12 or: gpg --default-key 0x12345678 --sign-key 0xABCDEF12.
Jun 27 2021
Jun 25 2021
Jun 22 2021
I did some test on Windows 10 using gnupg 2.2 with this patch and things work.
For testing ion Windows 10 you need to switch to "Legacy Console" and reboot.
I think that a patch like following is needed:
diff --git a/common/ttyio.c b/common/ttyio.c index c385700de..55468bdf0 100644 --- a/common/ttyio.c +++ b/common/ttyio.c @@ -236,7 +236,21 @@ w32_write_console (const char *string) n = wcslen (wstring);
When console font is not a Unicode font, it seems that the WriteConsoleW function may return ERROR_GEN_FAILURE.
Hello Mr. Koch,
Jun 21 2021
Jun 17 2021
Hello Mr. Koch,
Are you using Powershell or another non-standard shell? Which windows version are you using? Do you use default-key in gpg.conf? Do you have a smartcard inserted?
Jun 2 2021
With sqlite3 using -static-libgcc, I confirmed that GnuPG and its friends are built well with newer mingw on bullseye. And I lightly tested GnuPG on Windows.
Jun 1 2021
Ah, I realized that the build for sqlite3 in Speedo has a patch using -static-libgcc.
We use libgcc_s_sjlj-1.dll only for for gpg4win's C++ code which is gpgme's c++ binding and the Qt stuff.
May 19 2021
Funny thing is that I can't replicate it anymore with the current version (2.2.18-beta77). I tested it on two machines and things just worked. One machine had just one reader and the other had several virtual readers in addition to the scr3500. After adding --reader-port for the latter it worked as well. I don't think I had a Windows update in the meantime.
May 11 2021
On Windows, smartcard is also used by logon/logout and certificates handling. Those may be related.
May 10 2021
(I disabled the account of this boor)
I don't think that it is --pcsc-shared related; Andre reported that he noticed such a behaviour before we introduced this.
I wonder if PCSC_SHARE_SHARED is related or not.
Apr 23 2021
Apr 22 2021
Given that we don't yet support TPM for Windows you should go ahead and apply this patch. tpm should also be removed from the list of components.
Apr 15 2021
gpg4win 3.1 has no full Unicode support. You may try to install the new GnuPG 2.3 version on top of gpg4win to fix this problem or wait until we have releases gpg4win 4 which will come with GnuPG 2.3.
Mar 28 2021
yep, Should be fixed in libgpg-error/src/w32-gettext.c unless we want a way to retrieve the meat data. We can also and faster fix this in gnupg proper.
Mar 25 2021
Example from gpg.c:
ARGPARSE_s_n (oQuiet, "quiet", N_("be somewhat more quiet")), [...] ARGPARSE_s_n (oNoGreeting, "no-greeting", "@"),
The quiet option has a human readable description, but the no-greeting option does not have one. Consequently, gpgconf --list-options gpg gives the following result:
[...] quiet:0:0:be somewhat more quiet:0:0:::: no-greeting:0:3::0:0::::1 [...]
For comparison, on an English Linux system the options also look wrong, i.e. all options that are problematic in the German translation are "raw" option names enclosed in double quotes. It seems that the untranslated description of the options is already missing.
Btw this only occurs for some options: