Fix is released in Gpg4win-3.1.2
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 18 2018
Fix is released in Gpg4win-3.1.2
And 2.2 branch.
The problem is complicated because we would have to parse each multipart/mixed mail before we can know that the mime structure looks that way.
Fixed in master.
It's in 2.2.4 and 1.4.23.
Closing.
Jun 17 2018
Support was removed.
Patch committed to master in commit 5a80e755008bbb3f4c7f91ffccd38f26cd8b3960
Not to worry, we've all been pretty busy of late.
Jun 16 2018
I re-tested this with version 2.2.8 and the same result.
Jun 15 2018
I'll fix for the non-FQDN case.
I think that I identified the issue. This is the libdns (dirmngr/dns.c) problem when hostname is not FQDN.
If you change it to FQDN, you can see that it tries to search adding the domain name.
This was released with Gpg4win-3.1.1
For issues/19, it is also reported in T3374: gpg recv-keys fail if first dns server end up with "Connection refused".
This is fixed in master now.
I'm not sure if original reporter's problem is issues/19 or not.
Fixed in master.
It is indirectly reported at the upstream: https://github.com/wahern/dns/issues/19
I tested on Debian with local dnsmasq. For usual setting, no problem.
If /etc/resolv.conf has nameserver 127.0.0.1 and the service by dnsmasq somehow stops, and we have another nameserver nameserver somewhere-not-local the issues/19 matters.
Jun 14 2018
--shows-keys is not a debug command to show the inetrnals of an OpenPGP message. It does the same as creating an empty homedir, importing the keys and running -k. Thus there is no way to get to the internals of an OpenPGP messages.
i'm having trouble just assembling the two signatures over the subkey with 2.2.8 in a single homedir. in particular, when i try to do the following with a new, clean test GNUPGHOME, then i see only one signature on the subkeys afterward:
I've made the parsing less strict in LibTMCG: https://github.com/HeikoStamer/libtmcg/commit/be7963b33cf8bace9d031074521acc4e89930d33
thanks, that works for me. I look forward to seeing the patches :)
See T4012 for a patch to build with an older libgpg-error.
Although "certificate" is used for OpenPGP revocations, it is technically a signature.
can you let me know what you're planning so i can plan my work on enigmail?
test after system upgrades
Thanks.
So what I remembered was 1 year and 1 month off the real EOL date.
Jun 13 2018
Here is our announcement: https://lists.gnupg.org/pipermail/gnupg-announce/2018q2/000426.html
thus far every packet type has been a three-letter string, right? I'm looking at "Field 1" in doc/DETAILS. adding a 4-letter packet type seems like it could be trouble if someone has done the dumb thing of assuming the field is fixed-length.
Informed Debian security team about our change of libgcrypt.
A new installer for GnuPG with Libgcrypt 1.8.3 is now available.
Change done and pushed already.
Releases are now available. Next task is to build a new GnuPG Windows installer.
1.8.3 and 1.7.10 are now released. Announcement will follow later the day.