Page MenuHome GnuPG
Feed Advanced Search

Sep 8 2014

aheinecke added projects to T1711: glib 2.41 uses rand_s which is not available on all platforms: Windows, gpg4win, Windows 32, Bug Report.
Sep 8 2014, 12:30 PM · Bug Report, Windows 32, gpg4win, Windows

Sep 3 2014

aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

Not sure what you mean by "It is not useful for that purpose" what do you mean
by "It" and "that" in this context.

With regard to complaints there are reports about this that have been active
nearly all the time since this was broken by 2.2.0:
https://wald.intevation.org/forum/message.php?msg_id=2569&group_id=11

This thread triggered your initial opening of this issue.

I agree that wildcard / multifile it is not very important. But I think we
should fix it as it is a small annoyance and it worked with gpg 2.1.0. That it
stopped working was due to our switch to mingw-w64 and not due to a decision
made by us to disable this. So I would see this as a Bug.

Some more threads about this:
https://wald.intevation.org/forum/forum.php?thread_id=1119&forum_id=21&group_id=11
https://wald.intevation.org/forum/message.php?msg_id=3404

P.S.
Yes I dislike the message boards too but they are surprisingly active.

Sep 3 2014, 5:33 PM · Bug Report, Windows 32, gpg4win, Windows
werner added a comment to T1571: gpg --multifile and wildcards problem on Windows.

It is not useful for that purpose. This is probably the reason why we received
no complaints about it unless someone uses --multifile with filenames. It is
almost always wrong to do this.

Sep 3 2014, 4:56 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke claimed T1571: gpg --multifile and wildcards problem on Windows.
Sep 3 2014, 4:09 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

I disagree, all builtin windows tools do globbing so you expect it on the
command line. And as this is default for software that is built with visual
studio and with some versions of mingw it is more likely to see a software that
supports globbing then not.

With regards to quoting problems. I think that users would prefer some problems
instead of just "no". There is no xargs equivalent in Windows by default and so
you have to fall back to really ugly batch scripts that do this in for loops.

Yes one could argue that those users should use a "real shell" on a "real
system" ;-)

Well, it's part of 2.2.2 now, lets see if we get some feedback on this and maybe
for the next release we can revisit the question again if we should enable this
or not.

Sep 3 2014, 4:09 PM · Bug Report, Windows 32, gpg4win, Windows
werner added a comment to T1571: gpg --multifile and wildcards problem on Windows.

It would be rather surprising if just one tool does globbing on Windows but all
the otehrs don't do it. It may actually lead to bugs due to broken quoting in
mingw. I recall than many years ago we had a lot of problems with the ever
changing quoting in the globbing implementation.

In any case using globbing with --multifile is not a good idea at all. There is
always a limit on this and thus the proper way of handling this is to use xargs
or whatever the counterpart is on Windows.

Sep 3 2014, 3:58 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke reassigned T1571: gpg --multifile and wildcards problem on Windows from aheinecke to werner.
Sep 3 2014, 10:55 AM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

Tested this myself again. And I feel comfortable that this is fixed. Still I do
not know why this works now.

Werner can you take a look at the patch I've added for this:

http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=blob;f=patches/gnupg2-2.0.26/0001-Enable-wildcard-expansion-with-mingw-w64.patch;h=6c5b9f8b0794cf32ab909c0a340f81377dc3d42f;hb=HEAD

Is this something you would consider including in some form in gnupg or should I
move the patch into the generic gnupg patch directory?

Sep 3 2014, 10:55 AM · Bug Report, Windows 32, gpg4win, Windows

Aug 26 2014

aheinecke added a project to T1571: gpg --multifile and wildcards problem on Windows: Restricted Project.
Aug 26 2014, 10:47 AM · Bug Report, Windows 32, gpg4win, Windows
aheinecke updated subscribers of T1571: gpg --multifile and wildcards problem on Windows.
Aug 26 2014, 10:47 AM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

Now for 2.2.2 we've switched to a new dedicated buildsystem with a fully updated
debian wheezy whereas the old buildsystem was a debian unstable snapshot with
the same mingw Version: 2.0.3-1
I could not find an upstream bug or any indication that there was a fix for this.

But with beta-37 of 2.2.2 I was able to use wildcards on the command line.
I am out of my wits why this works now.

Emanuel: can you confirm that wildcards now work on the command line so that we
can mention this in the news and maybe look at integrating the patch into gnupg?
I'd like a different pair of eyes on that behavior. Maybe I've just messed up my
testsystem.

Aug 26 2014, 10:47 AM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

I've commited the patch to gpg4win so it will be part of the 2.2.2 release.

Thanks for summing up the other problems. I've added a reference to this issue
to the "Improve encoding handling" point in the backlog:
http://wiki.gnupg.org/Gpg4win/Wishlist

Aug 26 2014, 9:55 AM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg

Aug 25 2014

andreaerdna added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Thanks Andre for the patch!

I managed to build gpg4win with the patch added and I verified that it seems to
solve the problem reported by me and also in Issues 1373 and 1674!

But I'd like to summarize the problems related to the charset / codepage on MS
Windows of which I am aware, as a reminder:

  1. incorrect display of GPG 2 output translated into another language (also

reported in Issue 1373 and Issue 1674): fixed by your patch;

  1. passphrases (both for secret keys and symmetrical encryption) with non ASCII

characters set using GPG 1.4.18 are considered not valid using GPG 2.0.26 and
vice versa

  1. incorrect display of filenames with non ASCII characters (also in Issue 1409)
  1. GPG 2.0.26 and 1.4.18 ignore or weirdly comply with --utf8-strings, --no-

utf8-strings or --charset options for utf-8 encoding of encrypted filenames (see
Issue 1409)

  1. charset weirdness searching keyserver for some non-ASCII user IDs under non-

UTF-8 locales (see Issue 1514 - although relates to Linux it seems to occur also
on Windows, both CLI and GPA but not Kleopatra)

Hope this will help to improve the great GnuPG :-)

Aug 25 2014, 4:29 AM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
andreaerdna added a project to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows: gnupg (gpg14).
Aug 25 2014, 4:26 AM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg

Aug 21 2014

aheinecke added a comment to T1529: GpgOL for Outlook 2010+ does not read Address entrys from Exchange.

This should be working with gpgOl 1.2.1

As I don't have a test set up I'm setting this to resolved until someone complains.

Aug 21 2014, 7:30 PM · Bug Report, Windows 32, gpgol, gpg4win, Windows
aheinecke closed T1529: GpgOL for Outlook 2010+ does not read Address entrys from Exchange as Resolved.
Aug 21 2014, 7:30 PM · Bug Report, Windows 32, gpgol, gpg4win, Windows
werner added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Good anlysis. Thanks.
Feel free to put it as a patch into gpg4win.
I need to look closer at it because we have have the gettext code also in
libgpg-error. You should also send a DCO for GnuPG.

Aug 21 2014, 12:18 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Aug 21 2014, 12:07 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Pretty picture.

Aug 21 2014, 12:07 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

D211: 465_0001-Let-wchar_to_native-convert-to-console-codepage.patch

Aug 21 2014, 12:07 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke updated subscribers of T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.
Aug 21 2014, 12:07 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke assigned T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows to werner.
Aug 21 2014, 12:07 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

I've taken a look at this. The problem is that the working conversion code in
jnlib/utf8conv.c is not used on Windows but instead jnlib/w32-gettext.c does
it's own conversion to wchar and then back from wchar to the native codepage
which is simpler and should work.

But the conversion back used the wrong codepage. CP_ACP instead of the codepage
retuned by GetConsoleOutputCP. jnlib/utf8conv.c actually had a comment
explaining why it is neccessary to use GetConsoleOutputCP.

With this changed (see attached patch) I get correct output and can verify /
sign files with non-ascii filenames.

I think gnupg master behaves differently though and I don't have a test setup
for this so the patch is only against STABLE.

Werner any objections into including this patch into GnuPG / Gpg4Win?

Aug 21 2014, 12:07 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg

Aug 19 2014

andreaerdna added projects to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows: gpg4win, gnupg (gpg20).
Aug 19 2014, 2:36 AM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
andreaerdna renamed T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows from Charset / codepage problem in GnuPG 2.0.26 localized in italian on MS Windows to Charset / codepage problems in GnuPG 2.0.26 on MS Windows.
Aug 19 2014, 2:36 AM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
andreaerdna added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Thanks Werner. I had already done a search among the issues using the world "charset", but the 1373 issue was
not displayed.

However the bug occurs more problematically with passphrases: a secret key passphrase with non ASCII characters
set using GPG 1.4.18 for a given key is considered not valid using GPG v 2.0.26 to deal with the same key and
vice versa.
I think this problem may cause a lot of trouble to users.

The bug also occurs using filenames in which there are characters outside the ASCII block. This occurs also
setting LC_MESSAGES=C or LC_MESSAGES=en_US.UTF-8 (i.e. gpg -vvvv --verify C:\Users\Andrea\Downloads\gpg4win-
2.2.2-beta37_è_.exe.sig -> "gpg: assuming signed data in `C:\\Users\\Andrea\\Downloads\\gpg4win-2.2.2-
beta37_Þ_.exe'" in which are also wrongly displayed double backslashes instead of single) and also with gpg
1.4.18 (but without the double backslashes). Luckily this does not prevent the signature verification. It's
similar to T1409.

Some additional information:

the CHCP command executed at the Windows command prompt reports: "Tabella codici attiva: 850" (active codepage
850);

using the -vvvv option with the --verify command, gpg 2.0.26 and 1.4.18 report: "gpg: using character set
`CP850'".

Aug 19 2014, 2:36 AM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg

Aug 18 2014

werner added a project to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows: Duplicate.
Aug 18 2014, 9:23 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
werner added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

This is known. See the other bug report.

Aug 18 2014, 9:23 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
werner added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Duplicate of T1373

Aug 18 2014, 9:23 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
werner added projects to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows: Windows, Windows 32.
Aug 18 2014, 9:21 PM · gnupg (gpg14), gnupg (gpg20), Windows 32, Windows, gpg4win, Bug Report, gnupg
aheinecke removed a project from T1678: Pinentry-qt4 opens confirm dialog in the background: Restricted Project.
Aug 18 2014, 4:50 PM · Bug Report, Windows 32, pinentry, Windows
aheinecke closed T1678: Pinentry-qt4 opens confirm dialog in the background as Resolved.
Aug 18 2014, 4:50 PM · Bug Report, Windows 32, pinentry, Windows

Aug 13 2014

aheinecke removed a project from T1571: gpg --multifile and wildcards problem on Windows: Restricted Project.
Aug 13 2014, 12:35 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

Ok using the same compiler I've used a year ago I also get the same result I got
a year ago (phew I thought i screwed up the test).

But with the patch this should just work once we change the used mingw-version.
I could not find a bugreport or some other information where and when this is fixed.

Aug 13 2014, 12:35 PM · Bug Report, Windows 32, gpg4win, Windows

Aug 12 2014

aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

I've tested this again with the mingw version that is part of ubuntu and it works.

I've commited a patch to gpg4win to enable this and will check if this also
works with the debian wheezy mingw-crt version.

Aug 12 2014, 9:46 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a project to T1571: gpg --multifile and wildcards problem on Windows: Restricted Project.
Aug 12 2014, 9:46 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke claimed T1571: gpg --multifile and wildcards problem on Windows.
Aug 12 2014, 9:46 PM · Bug Report, Windows 32, gpg4win, Windows

Aug 6 2014

aheinecke added a project to T1678: Pinentry-qt4 opens confirm dialog in the background: Restricted Project.
Aug 6 2014, 3:33 PM · Bug Report, Windows 32, pinentry, Windows
aheinecke added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.

Thanks for the explanations.

Further analysis showed that the second call to AllowSetForeground window was
blocked by the ForegroundWindowLockTimeout. If you set this timeout to zero
everything worked as expected.

There is a discussion on this under:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/09fa16ba-c6ef-410d-bec2-a99a9b9a98d9/issue-with-foregroundlocktimeout-setforegroundwindow

Which suggests a solution of setting the foregroundlocktimeout to zero before
attempting to set the foreground window. I've found this solution not applicable
for our case as we run into the lock on "AllowSetForegroundWindow" and not when
actually setting the foreground Window.

Another workaround is to call AttachThreadInput on the current foreground thread
call SetForegroundWindow and then detach again. There might be problems with
this approach so it is just used as fallback. But it should resolve this problem
for now.

Aug 6 2014, 3:33 PM · Bug Report, Windows 32, pinentry, Windows
werner added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.

What I described is done for all pinentries.

Aug 6 2014, 10:32 AM · Bug Report, Windows 32, pinentry, Windows

Aug 5 2014

aheinecke added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.

Ok, thanks I'll check what happens if

  1. The agent thinks that the passphrase entered is too weak
  2. The agent starts another pinentry
  3. The agent sends "getinfo pid" to the pinentry (this i can see)
  4. ?
Aug 5 2014, 3:19 PM · Bug Report, Windows 32, pinentry, Windows
werner removed a project from T1516: gpgex crashing Windows explorer (64 bit): Restricted Project.
Aug 5 2014, 3:16 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex
werner closed T1516: gpgex crashing Windows explorer (64 bit) as Resolved.
Aug 5 2014, 3:16 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex
werner added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.
  1. The agent starts pinentry.
  2. The agent sends "getinfo pid" to the pinentry"
  3. The agents sends an "INQUIRE PINENTRY_LAUNCHED <pid>" to the caller.

4a. If the caller is gpg, gpg calls AllowSetForegroundWindow for the received
pid; gpg has been started via gpgme and gpgme has called ASFW for gpg.
4b. If the caller is gpgsm, it proxies the PINENTRY_LAUNCHED to gpgme which then
calls ASFG for the pid.

The different methods are required because gpg is a one-off process while gpgsm
may be used several times.

Aug 5 2014, 3:11 PM · Bug Report, Windows 32, pinentry, Windows
aheinecke added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.

Yes Kleopatra uses gpgme for key generation. Still I don't see how gpgme figures
into this sorry. Should gpgme start gpg-agent and ensure that it has the
setforeground window access right?

  1. The gpg-agent asks for a passphrase with pinentry -> set foreground window is

allowed.

  1. If that passphrase is weak it launches a new pinentry with a confirm dialog

-> set foreground window is not allowed.

And the agent does not have the right to call allowsetforegroundwindow. In the
first case I think this might be because another component gets the PID of the
pinentry and calls allowsetforeground window (have to do further debugging to
check this)

In the second case afaik only gpg-agent is involved and no one sets
allowsetforeground window on the pid of the second pinentry.

Aug 5 2014, 9:36 AM · Bug Report, Windows 32, pinentry, Windows

Aug 4 2014

werner added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.

BTW, gpgme 1.5.1 has a spawn interface which is better than to code your own in Qt.

Aug 4 2014, 3:36 PM · Bug Report, Windows 32, pinentry, Windows
werner added a comment to T1678: Pinentry-qt4 opens confirm dialog in the background.

It goes all the way back to GPGME via the assuan interface. grep for
_gpgme_allow_set_foreground_window. For GPG the assuan interface is not used.
We do it by passing our internal IOSPAWN_FLAG_ALLOW_SET_FG flag to the
gpgme-w32spawn.c helper which then uses this to call set foreground API.

Does Kleopatra always use gpgme?

Aug 4 2014, 3:34 PM · Bug Report, Windows 32, pinentry, Windows
aheinecke added projects to T1678: Pinentry-qt4 opens confirm dialog in the background: Windows, pinentry, Windows 32, Bug Report.
Aug 4 2014, 12:36 PM · Bug Report, Windows 32, pinentry, Windows

Jul 30 2014

werner added a comment to T1516: gpgex crashing Windows explorer (64 bit).

I won't call that leaking memory.

Jul 30 2014, 2:38 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex

Jul 28 2014

aheinecke added a comment to T1516: gpgex crashing Windows explorer (64 bit).

With your fix it no longer crashes. But you are leaking memory in case
default_homedir returns allocated memory from read_w32_registry_string or
standard_homedir with a successful call to w32_shgetfolderpath.

As the result should be cached in the static variable this is probably not an
issue..

Jul 28 2014, 5:31 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex
werner added a comment to T1516: gpgex crashing Windows explorer (64 bit).

I just pushed a fix.

The problem with gpgme is that we need to stop the Explorer if we want to update
or uninstall gpgme. Given tha we can't use gpgex with the portable version
anyway, I think it is better to keep the existing code and don't switch to gpgme.

Jul 28 2014, 10:21 AM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex
werner added a project to T1516: gpgex crashing Windows explorer (64 bit): Restricted Project.
Jul 28 2014, 10:21 AM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex

Jul 25 2014

aheinecke added a comment to T1516: gpgex crashing Windows explorer (64 bit).

Using gpgme would be nice of course to avoid duplicated functionality (this same
stuff is also implemented in gpgol although without the bug) but remember that
we would then also need a x64 version of gpgme.

Jul 25 2014, 3:52 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex
werner added a comment to T1516: gpgex crashing Windows explorer (64 bit).

The bug is pretty obvious. I consider to rewrite it by calling gpgconf
--list-dirs to get the home directory. This would be simliar to what we do in
gpgme. Or well, we could link to to gpgme to and make use of its higher level
interface.

Jul 25 2014, 3:31 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex

Jul 24 2014

aheinecke added a comment to T1516: gpgex crashing Windows explorer (64 bit).

Thanks for looking at this. If you like I could test your fixes. I currently
have a build setup and a test setup where I can reproduce the crash.

Btw. Maybe I don't understand c++ enough but afaik this just makes no sense and
is broken:

  try { name = ((string) dir) + "\\S.uiserver"; } catch (...) {}

should be rather something like:
if (dir)
name = string(dir) + "\\S.uiserver";

Jul 24 2014, 9:30 AM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex

Jul 23 2014

werner added a comment to T1516: gpgex crashing Windows explorer (64 bit).

I have some fixes sitting here in my local repo. I need to check them.

Jul 23 2014, 3:17 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex
aheinecke added projects to T1516: gpgex crashing Windows explorer (64 bit): Windows, gpg4win, Windows 32, Windows 64.
Jul 23 2014, 3:05 PM · Windows 64, Windows 32, gpg4win, Windows, Bug Report, gpgex

Jan 28 2014

werner added a project to T1582: Error in make check -- compiling with MinGW for Windows: Mistaken.
Jan 28 2014, 5:30 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows
werner changed Due Date from Dec 16 2013, 12:00 AM to Dec 15 2013, 1:00 AM on T1582: Error in make check -- compiling with MinGW for Windows.
Jan 28 2014, 5:30 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows
werner closed T1582: Error in make check -- compiling with MinGW for Windows as Resolved.
Jan 28 2014, 5:30 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows

Dec 19 2013

erich_carlmann added a comment to T1582: Error in make check -- compiling with MinGW for Windows.

sorry can't delete

Dec 19 2013, 4:13 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows

Dec 16 2013

erich_carlmann added projects to T1582: Error in make check -- compiling with MinGW for Windows: Windows, gnupg (gpg14), Windows 32, gnupg, Bug Report.
Dec 16 2013, 6:30 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows
erich_carlmann set Version to 1.4.15 on T1582: Error in make check -- compiling with MinGW for Windows.
Dec 16 2013, 6:30 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows
erich_carlmann set Due Date to Dec 16 2013, 12:00 AM on T1582: Error in make check -- compiling with MinGW for Windows.
Dec 16 2013, 6:30 PM · Mistaken, Bug Report, gnupg, Windows 32, gnupg (gpg14), Windows

Nov 22 2013

aheinecke reassigned T1571: gpg --multifile and wildcards problem on Windows from aheinecke to werner.
Nov 22 2013, 7:13 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

Mmmh when I run:

#include <stdio.h>
int _dowildcard = -1;
int main (int argc, char **argv)
{

int i = 0;
for ( i = 0; i< argc; i++) {
    printf("%s\n", argv[i]);
}
return 0;

}

With the command line *.* it just prints "*.*". Linking with CRT_glob.o directly
also leads to the same result.

Nov 22 2013, 7:13 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke added a comment to T1571: gpg --multifile and wildcards problem on Windows.

Hi,
there is apparently a compile option "enable-wildcard" for the mingw-w64 c runtime.

But from:
http://mingw-w64.sourcearchive.com/documentation/0~20100125-3/wildcard_8c-source.html

I take it that you can also enable it in the program by defining int _dowildcard

-1;

I'll test it and let you know if this worked.

Nov 22 2013, 6:32 PM · Bug Report, Windows 32, gpg4win, Windows
aheinecke claimed T1571: gpg --multifile and wildcards problem on Windows.
Nov 22 2013, 6:32 PM · Bug Report, Windows 32, gpg4win, Windows
werner set Version to 2.2.0 on T1571: gpg --multifile and wildcards problem on Windows.
Nov 22 2013, 10:41 AM · Bug Report, Windows 32, gpg4win, Windows
werner added projects to T1571: gpg --multifile and wildcards problem on Windows: Windows, gpg4win, Windows 32, Bug Report.
Nov 22 2013, 10:41 AM · Bug Report, Windows 32, gpg4win, Windows

Oct 24 2013

werner removed a project from T1525: Gpa crashes on windows when copying a key to the clipboard: Restricted Project.
Oct 24 2013, 7:43 AM · Windows 64, Bug Report, gpa, Windows 32, Windows
werner closed T1525: Gpa crashes on windows when copying a key to the clipboard as Resolved.
Oct 24 2013, 7:43 AM · Windows 64, Bug Report, gpa, Windows 32, Windows

Sep 2 2013

emanuel added a comment to T1324: Encryption of an folder with umlauts failed.

works with Gpg4win 2.2.0. But there is a failure after decrypting folder with
umlauts: see gpg4win wald issue #6451
(https://wald.intevation.org/tracker/index.php?func=detail&aid=6451&group_id=11&atid=126)

Sep 2 2013, 4:47 PM · Bug Report, Windows 32, gpgex, gpg4win, Windows
emanuel closed T1324: Encryption of an folder with umlauts failed as Resolved.
Sep 2 2013, 4:47 PM · Bug Report, Windows 32, gpgex, gpg4win, Windows

Aug 22 2013

aheinecke added projects to T1529: GpgOL for Outlook 2010+ does not read Address entrys from Exchange: Windows, gpg4win, gpgol, Windows 32, Bug Report.
Aug 22 2013, 3:12 PM · Bug Report, Windows 32, gpgol, gpg4win, Windows
aheinecke set Version to 1.2.0 on T1529: GpgOL for Outlook 2010+ does not read Address entrys from Exchange.
Aug 22 2013, 3:12 PM · Bug Report, Windows 32, gpgol, gpg4win, Windows

Aug 16 2013

werner added a project to T1525: Gpa crashes on windows when copying a key to the clipboard: Restricted Project.
Aug 16 2013, 4:18 PM · Windows 64, Bug Report, gpa, Windows 32, Windows
werner added a comment to T1525: Gpa crashes on windows when copying a key to the clipboard.

Fixed in d3f20e7. Applied patch to gpg4win as well.

Aug 16 2013, 4:18 PM · Windows 64, Bug Report, gpa, Windows 32, Windows
aheinecke added a comment to T1525: Gpa crashes on windows when copying a key to the clipboard.

Aug 16 2013, 12:52 PM · Windows 64, Bug Report, gpa, Windows 32, Windows
aheinecke added a comment to T1525: Gpa crashes on windows when copying a key to the clipboard.

In the backtrace gpa_backtrace2.png you can see that the crash happens:
https://bugzilla.gnome.org/show_bug.cgi?id=696232

If we apply the patch it no longer crashes, but as the error handling in that
patch is just to abort, the text is not copied into the clipboard and we do not
get an error in GPA.

So still some more debugging why invalid utf-8 data is sent from gpa.
As the data worked on comes from GPA and "should" be valid utf-8

Aug 16 2013, 12:52 PM · Windows 64, Bug Report, gpa, Windows 32, Windows

Aug 14 2013

aheinecke added a comment to T1525: Gpa crashes on windows when copying a key to the clipboard.

Backtrace attached. Sorry that it is an image but windows was blocking me from
copying the gdb output to the clipboard.

Aug 14 2013, 6:23 PM · Windows 64, Bug Report, gpa, Windows 32, Windows
aheinecke added a comment to T1525: Gpa crashes on windows when copying a key to the clipboard.

Aug 14 2013, 6:23 PM · Windows 64, Bug Report, gpa, Windows 32, Windows
aheinecke added projects to T1525: Gpa crashes on windows when copying a key to the clipboard: Windows, Windows 32, gpa, Bug Report, Windows 64.
Aug 14 2013, 6:07 PM · Windows 64, Bug Report, gpa, Windows 32, Windows

May 1 2013

werner added a project to T1012: w32 / validating signature crashes GPA which tries to dereference a null-pointer: Too Old.
May 1 2013, 11:34 AM · Too Old, Bug Report, gpa, Windows 32, Windows
werner closed T1012: w32 / validating signature crashes GPA which tries to dereference a null-pointer as Resolved.
May 1 2013, 11:34 AM · Too Old, Bug Report, gpa, Windows 32, Windows
werner added a comment to T1012: w32 / validating signature crashes GPA which tries to dereference a null-pointer.

Let's assume that the problem was in the glib library and has been fixed in the
meantime. I will soon release a new Gpg4win version with the latest stable glib
version. Feel free to reopen if you still encounter this problem.

May 1 2013, 11:34 AM · Too Old, Bug Report, gpa, Windows 32, Windows

Sep 26 2012

werner added a comment to T1439: Windows: race condition on random_seed.

Yeah sure, I meant "NOT a problem".

Yes I know what you mean. But without locking you will never be able
to get it right.

As you noted there is actually a problem with Libgcrypt under
Windows. In Libgcrypt we lock the seed file and thus the fatal error
is the right thing to do. But.....

  #ifdef __GCC__
  #warning Check whether we can lock on Windows.
  #endif
  #if LOCK_SEED_FILE

Thus we should implement locking for Windows. The problem here is
that there is no portable advisory locking in Windows. And frankly our
fcntl locking approach does not work on all Unices either and worse it
does not work if the home partition is on certain remote file systems.

The only solution I see is to employ the new dotlock code from GnuPG
here. It is slower than fcntl locking but very portable.

I don't think we will fix this in gpg 1.4.

Sep 26 2012, 3:15 PM · libgcrypt, Bug Report

Sep 18 2012

jegrp added a comment to T1439: Windows: race condition on random_seed.

This is known but a problem from a security POV.

I suppose you mean "NOT a problem"? I think it might be a problem in
opportunistic encryption scenarios if gpg encryption failures caused by
random_seed access conflicts are ignored like failures caused by missing keys.
But usually it's just a nuisance like any other randomly failing program.

The non-locking read is on purpose - if it works: okay. Otherwise we
re-generate a seed file.

I see that the code tries to tolerate access conflicts, but there's still a race
condition if the random_seed file is truncated between fstat() and read(). The
read() error handling is incomplete. Maybe this pseudo-patch explains best what
I mean:

diff -ru gnupg-1.4.12/cipher/random.c gnupg-1.4.12/cipher/random.c

  • gnupg-1.4.12/cipher/random.c 2012-01-24 09:45:41.000000000 +0100

+++ gnupg-1.4.12/cipher/random.c 2012-09-18 19:47:54.449578800 +0200
@@ -492,11 +492,17 @@

    do {
	n = read( fd, buffer, POOLSIZE );
    } while( n == -1 && errno == EINTR );
  • if( n != POOLSIZE ) {

+ if( n == -1 ) {

	log_fatal(_("can't read `%s': %s\n"), seed_file_name,strerror(errno) );
	close(fd);
	return 0;
    }

+ else if ( n == 0 ) {
+ ... handle like sb.st_size == 0
+ }
+ else if ( n != POOLSIZE ) {
+ ...
handle like sb.st_size != POOLSIZ
+ }

     close(fd);

Yes, we could do the file locking

Proper locking would be the ideal solution, but a better read() error handling
would already be sufficient to avoid the sporadic fatal errors on random_seed
accesses.

and iirc, we do this in libgcrypt (GnuPG-2).

I'm just checking this and ... sorry, no. The gpg2.exe from Gpg4win 2.1.0 shows
the very same error:

note: random_seed file is empty
note: random_seed file is empty
Fatal: can't read `C:/Dokumente und
Einstellungen/jechternach/Anwendungsdaten/GnuPG /random_seed': No such file or
directory

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
note: random_seed file is empty

Sep 18 2012, 7:52 PM · libgcrypt, Bug Report

Sep 17 2012

werner added a comment to T1439: Windows: race condition on random_seed.

This is known but a problem from a security POV. The seed file is a cache. If
the seed file can't be read a new one is created. Right, there might be a
performance issue but at least on Windows this is not as severe as on certain
Linux systems.

The non-locking read is on purpose - if it works: okay. Otherwise we
re-generate a seed file. Yes, we could do the file locking and iirc, we do this
in libgcrypt (GnuPG-2).

The error on short reads is also on purpose. We want those 600 bytes at once
and nothing else. If another process is writing the seed file we may see the
short reads. But in this case there is no clear answer waht to do - thus we
assume the "no seed file" case.

Sep 17 2012, 2:59 PM · libgcrypt, Bug Report
werner lowered the priority of T1439: Windows: race condition on random_seed from High to Normal.
Sep 17 2012, 2:59 PM · libgcrypt, Bug Report
werner added a project to T1439: Windows: race condition on random_seed: gnupg.
Sep 17 2012, 2:59 PM · libgcrypt, Bug Report

Aug 29 2012

jegrp added projects to T1439: Windows: race condition on random_seed: Windows, Windows 32, Bug Report.
Aug 29 2012, 6:03 PM · libgcrypt, Bug Report
jegrp set Version to 1.4.12 on T1439: Windows: race condition on random_seed.
Aug 29 2012, 6:03 PM · libgcrypt, Bug Report

Jan 3 2012

werner closed T1010: Cache file rename problem under W32 as Resolved.
Jan 3 2012, 6:55 PM · gpg4win, Bug Report, Windows 32, Windows, dirmngr
werner removed a project from T1010: Cache file rename problem under W32: Restricted Project.
Jan 3 2012, 6:55 PM · gpg4win, Bug Report, Windows 32, Windows, dirmngr

Jul 4 2011

werner changed Version from 1.4.11 (and 1.4.10) to 1.4.11 on T1298: GPG hangs after Signing a key.
Jul 4 2011, 12:28 PM · Mistaken, Windows 32, Info Needed, Windows, Bug Report, gnupg
werner closed T1298: GPG hangs after Signing a key as Resolved.
Jul 4 2011, 12:28 PM · Mistaken, Windows 32, Info Needed, Windows, Bug Report, gnupg

Jul 1 2011

Wolfgang_Schlage added a comment to T1298: GPG hangs after Signing a key.

Thanks, Werner, for your reply and your suggestions. I'll have a look at the
GPGME solution.

Jul 1 2011, 2:43 PM · Mistaken, Windows 32, Info Needed, Windows, Bug Report, gnupg
Wolfgang_Schlage reopened T1298: GPG hangs after Signing a key as "Open".
Jul 1 2011, 2:43 PM · Mistaken, Windows 32, Info Needed, Windows, Bug Report, gnupg
werner added a project to T1117: German Umlaute are wrong in console: Feature Request.
Jul 1 2011, 12:29 PM · Feature Request, Windows 32, Windows, gnupg