Yes, that did the trick for me!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 20 2018
Nice, then my commit should fix the issue here.
Yes, definitely the real reason is in the inline editor.
I can't confirm the regression yet. For me (albeit with Outlook 2016) preselecting sign / encrypt based on the options works for reply and forward. But only as long as the Mail is opened in a dedicated window.
It's manually written one in Debian:
https://salsa.debian.org/debian/gnupg2/blob/debian/master/debian/gpg-check-pattern.1
I manually configure IPv6 only environment, and now (forthcoming 2.2.9), it works fine for me.
So, I move this state to Testing.
Thank you for your fast fix!
2.2.1-beta2 works as expected!
- dirmngr fix for --recursive-resolver: rG5b40338f1276: dirmngr: Fix recursive resolver mode.
- After the release, we can ask using this mode not to use nameserver in /etc/resolv.con, but resolve by libdns directly
- Possibly, these bug reports are related: T2968: gpg --search: Connection closed in DNS, T3168: dirmngr: gpg: keyserver receive failed: No keyserver available, T3517: dirmngr: retry without SRV due to buggy routers
Applied to 2.2 branch.
As written in T2438:
I think that this is same issue of T2438: dirmngr fails repeatedly with "invalid argument", without kicking the host from its list.
Merging.
For the problem in the last comment, it was fixed in T2928: stop fetching PTR records entirely.
For the original issue, it looks that EINVAL is returned by the system call of connect(2).
That's quite strange, but, it was possible for IPv6.
Good. I don't think there is any reason to select the ephemeral port in user space (by default).
So, I disabled the feature for all OSes.
Jun 19 2018
Hi Werner,
I have performed some experiments on the issue I have and the following are the results:
Do we have an update on this? I seem to be having similar issue. Cannot import a key from my old gpg 1.x version to gpg 2.x version
could i get feedback on this ticket? a simple, clean patch is available, and i don't understand what is blocking it.
@gniibe Thank you very much!
I've tested the change on Windows 7 and Windows 10 and the Firewall warning is indeed gone with this.
I found dirmngr tries to bind some random port. It might be the cause.
As expected it was a very clear bug. We assign a NULL pointer to a string and then use that string.
Thank you for the report and the logs! A minor note: For future reports please leave the priority on "Needs Triage" we use this as a marker for issues no developer has looked at previously.
To avoid releasing incomplete tarballs this release should also be built from the source package and no longer from the git tag.
Fixed in repo (master and 1.8 branch).