Fri, Oct 23
Only enabled for UNIX #ifdef/#else/#endif
Wed, Oct 21
Sat, Oct 10
I finished the Italian translation of the GnuPg 2.2 file.
I need help, can you please update the source project with this translation? I am a beginner, unable to do this.
I attach files translated into Italian
Thu, Oct 8
diff --git a/agent/findkey.c b/agent/findkey.c index fa9e5b548..eec85ba67 100644 --- a/agent/findkey.c +++ b/agent/findkey.c @@ -996,7 +996,10 @@ agent_key_from_file (ctrl_t ctrl, const char *cache_nonce, if (r_passphrase) *r_passphrase = NULL;
Tue, Oct 6
We understand the problem, it's a regression from August. For T4083 we changed an internal function to better work with Windows UTF-16 filenames in preperation to at some point fully support UTF-16 and only use the wide character functions as system calls.
But that broke places where internally the local 8 bit encoding was still used.
I can reproduce this.
The umlaut is displayed incorrectly on the command line (cmd.app) when the keybox file is created.
(This may or may not be relevant.)
Mon, Oct 5
Should not be too complicated.
Part of the task is the plumbing for that in GPGME of course, I'm not sure if werner will do the core "C" part directly or if you could do this also. But first let's get it added to GnuPG.
Mon, Sep 28
With 2.3 we add the keyboxd which uses sqlite (and thus indices) as database. This makes lookups much much faster and avoids problems with several processes accessing the pubring.kbx. If you want to try this you can do so with 2.3:
Sep 10 2020
It should be possible to apply the patch rG7de9ed521e516879a72ec6ff6400aed4bdce5920
for 2.2 also to older 2.1 or 2.2 versions,
Sep 9 2020
That keeps the group permissions of an existing directory. Needs to be backported to 2.2
The fix we have there has the problem that it forcefully changes the permissions. Consider the case that for example that group access was provided which will currently be reset with each start of gpg-agent.
--locate-external-keys exists since 2.2.17 and ignores the local keys.
Sep 4 2020
for the fixed Gpg4win 3.1.13
Sep 3 2020
Sep 2 2020
Aug 29 2020
FWIW, here an example of warnings we use. Yes it starts with -Wall but there are a couple of more specific warnings and at a few places we even use pragmas to disable warnings. And it depends on the compiler version used.
Aug 28 2020
-Wall is not a good idea in general because it is too unspecific. This is why we have a list of useful warning and >warnings we ignore with gcc.
-Wall is not a good idea in general because it is too unspecific. This is why we have a list of useful warning and warnings we ignore with gcc.
I found the bug by compiling the package with C/C++ compiler clang and flag -Wall.
Fixed in gnupg and gpgme. it is not serious because that is just a failsafe check; libksba creates these strings and it does it correctly.
We have the same flaw in gnupg.
diff --git a/common/utf8conv.c b/common/utf8conv.c index 7804dbfcd..bdab225a9 100644 --- a/common/utf8conv.c +++ b/common/utf8conv.c @@ -138,7 +138,7 @@ handle_iconv_error (const char *to, const char *from, int use_fallback) native encoding. Nowadays this seems to be the best bet in case of errors from iconv or nl_langinfo. */ active_charset_name = "utf-8"; - no_translation = 0; + no_translation = 1; use_iconv = 0; } }