- User Since
- Mar 27 2017, 4:49 PM (138 w, 3 d)
Apr 5 2019
I did not yet implement the use of "key origin" in Enigmail. I don't believe that it adds much value, because I anyway need to track more details about autocrypt keys separately from the keyring (such as the peer-state).
Feb 23 2019
I could reproduce the problem (by chance) now, because I started a VM I didn't use for a while:
Feb 18 2019
Could it be possible that it's a 32/64 bit issue?
Is this with the /MINIMAL flag?
Jan 26 2019
May 30 2018
I have changed visibility of the bug, as I think you can do a lot more with this than Marcus imagined.
May 29 2018
This looks similar to the "multiple plaintext" issue that we had in Feb. / March 2007.
Apr 1 2018
Jan 27 2018
It turned out to be a bug in Enigmail. The "," in the key list s wrong.
Oct 13 2017
Werner, so what do you suggest? Does Enigmail (and any other tool using gpg, and actually also across tools) need to make sure that there are no concurrent calls to gpg of the type that could lead to adding a new key in the keyring?
Aug 3 2017
It looks like this was on my side. I can't reproduce it anymore; in other words dirmngr survives changes to DNS servers now.
Jul 31 2017
You're right, stat() works correctly. I created a small tool that implements the same logic. For some reason dirmngr is still not able to find the DNS server after suspend/resume in combination with changed locations. I still get "no route to host" errors.
Jul 30 2017
Jul 2 2017
Jul 1 2017
Jun 29 2017
Dec 24 2015
Dec 3 2009
yes, it's the official binary release from ftp.gpg4win.org.
That's gpg2 2.0.12, installed as part of gpg4win 2.0.1 (binary version installed).