The default for the timeout are 100 seconds. I will chnage that to 15 seconds which is the same what we use for keyservers.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 7 2017
Nov 6 2017
Also failed to replicate on Windows-7 using a dedicated laptop.
Nov 3 2017
I tested for several days with logging enabled but was not able to replicate it again. Then I tried again w/o logging and couldn't replicate it either.
Oct 28 2017
Hi,
I have tried this on Windows 10 (1511,1703,1709&RS4TP)
Gpg4win Version 3.0.0
Regards
Hi,
I was using Windows 7 Professional.
The last version that worked was gpg4win 2.3.4 (I didn't try any beta or rc), and encryption/decryption works fine for single files.
Oct 27 2017
Oct 26 2017
Oct 24 2017
I am closing this bug report, as I can't get feedback to fix something.
Oct 22 2017
Can you please try again with the standard shell (and not the power shell)?
Oct 20 2017
gniibe: Can you check the status?
I can replicate this now. Unfortunately without logging enabled.
Oct 19 2017
Here is a part of the log inline:
Additional report in https://wald.intevation.org/forum/message.php?msg_id=5308
Oct 16 2017
I added a Workaround in the Wiki: https://wiki.gnupg.org/Gpg4win/releases/3.0/notes
Oct 11 2017
... gpg-agent hangs. After cancelling the process it works again ...
Oct 10 2017
Sorry, I haven't waited long enough.
It's happened again. After leaving Thunderbird open for a while, when consulting another encrypted email, the window asking for the password does not appear and does nothing.
I need Gpg4Win, I'm going back to Gpg4Win 2.3.4
I think it might be a cleanup problem.
If you uninstall Gpg4Win 2.3.4, restart the computer, and then install Gpgp4Win 3.0.0, everything works correctly.
gpg-agent.conf actual content:
Does anyone of you have a gpg-agent.conf and if so, what options are set?
It works correctly when installed and executed.
After a period of inactivity and with Thunderbird still open, it stops working.
With Gpg4Win 2.3.4 it works correctly.
Oct 5 2017
Sep 28 2017
GnuPG is definitely not affected. I do my release test on Vista Ultimate Pro (or whatever it was called)
Someone described this issue with Windows Vista as well.
Sep 26 2017
CancelIoEx is supported by Vista.
Sep 25 2017
Sep 22 2017
Just to inform that it is not a single problem.
I recognized exactly the same behaviour.
After terminating the gpg-agent task everything works as aspected (up to the next non-activity phase).
64-bit Windows 7 Enterprise, Outlook 2010, GPG4Win Version 3.0.0-gpg4win-3.0.0.
Sep 6 2017
Please try: rA87c2bb5708ff: We can't support fd passing, if the system doesn't support it.
It disables the particular test.
I think that file descriptor passing is not supported on Cygwin.
We should disable the feature of libassuan.
Sep 4 2017
No, there isn't any error message or output, and it not accept any input.
Here is a GIF capture, but may not helpful.
dirmngr is meanwhile an integral part of GnuPG. The old 1.1 dirmngr is entire obsosolete and won't do what gpg expects from it. To better diagnose the problem you can do this:
Aug 31 2017
Aug 14 2017
Aug 9 2017
Aug 8 2017
In fact, on Windows you would need to have a system service. We did this in the past for the dirmngr but remove that feature due to possible security problems and problems during installation.
That is correct, gpg-agent does not daemonize on Windows if --daemon is given, it is simply not implemented.
Jul 27 2017
Jul 21 2017
Jul 20 2017
Jul 13 2017
Without more information, we can not act on this.
Jul 12 2017
Given that 2.0 reaches EOL in 6 months and the bug has been here for ages, I won't backport it to 2.0 anymore.
Jul 3 2017
No I don't recall any such problems, sorry.
Jul 1 2017
Jun 23 2017
GpgOL has even been revamped 2 times since then.
Jun 22 2017
Is this still an issue?
Jun 13 2017
Jun 2 2017
I just released 1.7.7
Jun 1 2017
werner, a quick question: what is the ETA of the new realease? I'm asking to see whether should I apply a temporary patch for the Windows64 build, or rather wait for the new release?
May 30 2017
Thank you werner for the quick reply!
Good catch. Only on Windows64 sizeof(int)==sizeof(long) and thus the generic definition does not work.
Fixed in master and 1.7: rC7a339b1fc94cbda738cf7712830e783faa0e325e
Hi werner, I have just managed to find a solution and its really weird.
I have seen that on this platform, the mpi-asm-defs.h is being linked from the generic folder and not from the AMD64 folder. All other asm files are nicely linked fro the AMD64 folder. Here is the relevant part from the build log:
May 23 2017
Fixed in npth 1.4.
May 21 2017
According to @MFPA still a problem on 2.1.21.
May 14 2017
Found the problem and fixed it. The Problem is described in the commit. Basically glib always assumed it gets UTF-8 Encoded filenames even if they were provided in system locale through double click / open with / command line / drag & drop.
GpgEX is now also compiled with ASLR + DEP. I still have to check some other binaries of Gpg4win before I close this task but I no longer see it as blocking a 3.0 release where I wanted to have this included.
Apr 25 2017
Talked to Werner about this. He still has concerns that this is wrong because an application should not do globbing itself and only changing this in gpg.exe is inconsistent. It also might be a security problem as most users won't use the double dash to seperate arguments from filenames.
Apr 24 2017
Added this to 3.0 because I don't want to release any known crashes.
I just commited the fix I had in gpg4win 2e71bf3. I don't see how this is objectionable as it changes the behavior back to what we had before we switched to building on jessie and is a minor ifdef.
Apr 21 2017
Apr 20 2017
Had same problem with waiting for .../gnupg/pubring.gpg - changed back to version 2.1.19, too [Windows 7, 32bit]
I confirmed that mingw-w64 version 1.0 defines timespec.
So, for older versions of mingw-w64, we need a fix to avoid errors.
But, your suggestion of __MINGW32__ != 1 seems wrong to me (I think it is always defined as 1).
Apr 19 2017
Apr 7 2017
Apr 4 2017
Mar 30 2017
Feb 14 2017
Jan 23 2017
Fixed in 6f02133bb07726afa6950e5b4685e75621276e60 by backporting a fix from
gpg-error.
After testing on Windows this problem is not resolved for Windows (I agree that
it's resolved for posix).
The issue there that I see now is not that it's a race between changing the
setting and immediately reading it again but that sometimes the communication
between gpgme and gpgconf fails.
See attached file no-read.txt for some debugging on this. GPGME writes a changed
option to gpgconf but gpgconf does not read it. I've used OutputDebugString and
DbgView to have syncronized debug output over process borders.
Not 100% reproducible but on my test system it fails very often.