dirmngrProject
ActivePublic

Members

  • This project does not have any members.

Watchers

  • This project does not have any watchers.

Recent Activity

Tue, Mar 19

wheelerlaw added a comment to T3065: dirmngr: proxy issues with dnslookup causing failure.

Also might I add, this used to work perfectly fine in gnupg14. It seems that somewhere along the line a regression was introduced that is causing this erroneous non-compliant behavior in the HTTP client.

Tue, Mar 19, 6:18 PM · gnupg (gpg22), dns, dirmngr
wheelerlaw added a comment to T3065: dirmngr: proxy issues with dnslookup causing failure.

Why? Your explanation is invalid because it implicates dirmngr's HTTP client as not comforming to the spec laid out by the RFC. I've quite clearly explained--and backed up with the spec itself--that when a proxy variable is configured, a client should not be doing DNS lookup of the destination hostname. Is there something about that you are not understanding?

Tue, Mar 19, 6:13 PM · gnupg (gpg22), dns, dirmngr
werner added a comment to T3065: dirmngr: proxy issues with dnslookup causing failure.

Please show an example regarding something else than a failed access to a pool of keyservers. I explained why it can't work for pools for you.

Tue, Mar 19, 7:59 AM · gnupg (gpg22), dns, dirmngr

Mon, Mar 18

wheelerlaw reopened T3065: dirmngr: proxy issues with dnslookup causing failure as "Open".

Yes you can, and no you do not. Don't believe me? Then read the spec. At no point does the spec say that there is "nothing that can be done" when a hostname cannot be resolved when connecting through a proxy. In fact, it states precisely the opposite, describing the exact procedure a client should take when making a request through a proxy. See section 5.3, paragraph 3:

Mon, Mar 18, 9:21 PM · gnupg (gpg22), dns, dirmngr
werner edited projects for T3257: dirmngr cannot set port for nameserver, added: Feature Request; removed gnupg (gpg22), Bug Report.
Mon, Mar 18, 7:30 PM · Feature Request, dirmngr
werner removed a project from T2398: finger support using SRV DNS records: gnupg (gpg22).
Mon, Mar 18, 7:29 PM · gnupg, Feature Request, dirmngr
werner closed T2908: dirmngr can't be build w/o LDAP as Wontfix.
Mon, Mar 18, 7:28 PM · gnupg (gpg22), dirmngr, Bug Report, gnupg
werner closed T3065: dirmngr: proxy issues with dnslookup causing failure as Invalid.

No we can't we need to know the IP addresses to handle the pools. I have given a workaround for you in my previous comment. You can also use install Tor which we can use for DNS resolving.

Mon, Mar 18, 7:26 PM · gnupg (gpg22), dns, dirmngr

Wed, Mar 13

wuximeniyu added a comment to T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached.

There is a solution for it:

Wed, Mar 13, 9:55 PM · Keyserver, Feature Request, dirmngr

Thu, Feb 28

aheinecke added a comment to T4380: GpgSM: CRL access not possible due to Tor mode.

Btw. I only noticed this now as I always had "disable-tor" in my config but recently removed it for testing.

Thu, Feb 28, 7:59 AM · Bug Report, dirmngr, S/MIME
aheinecke created T4380: GpgSM: CRL access not possible due to Tor mode.
Thu, Feb 28, 7:59 AM · Bug Report, dirmngr, S/MIME

Mon, Feb 25

gniibe added projects to T3381: dirmngr won't start on Windows 10 with admin level account: Testing, libassuan.
Mon, Feb 25, 3:37 AM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report

Feb 9 2019

kristianf closed T4354: dirmngr should send "fingerprint=on" to keyservers as Resolved.

So, the keyserver operator had thrown in a hockeypuck server in the pool, causing this.. While the keyserver remains in the exclude list until confirmation it has been resolved, that explains the behavior and it has been made clear that separate software needs to use different names in the future.

Feb 9 2019, 8:43 PM · dirmngr, Keyserver, Bug Report

Feb 4 2019

werner updated subscribers of T4354: dirmngr should send "fingerprint=on" to keyservers.

@kristianf we talked about this on Saturday evening. Would you be so kind and have a quick look at the problem with the hu server?

Feb 4 2019, 5:45 PM · dirmngr, Keyserver, Bug Report

Feb 1 2019

steve added a comment to T4354: dirmngr should send "fingerprint=on" to keyservers.

Hi Werner and thanks for looking into this.

Feb 1 2019, 10:32 AM · dirmngr, Keyserver, Bug Report

Jan 30 2019

werner edited projects for T4354: dirmngr should send "fingerprint=on" to keyservers, added: Keyserver, dirmngr; removed Feature Request.

According to sks-keyservers.net both servers you mention run the very same software. Thus I would like to understand why you think they require the use of a legacy option.

Jan 30 2019, 3:22 PM · dirmngr, Keyserver, Bug Report

Jan 25 2019

werner added a commit to T3381: dirmngr won't start on Windows 10 with admin level account: rA75770b1131e1: socks5: Fix compiler warning on Windows..
Jan 25 2019, 1:55 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
gniibe added a commit to T3381: dirmngr won't start on Windows 10 with admin level account: rA5e48116051a4: socks5: Implement timeout to detect bogus service..
Jan 25 2019, 4:23 AM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report

Jan 24 2019

aheinecke added a subtask for T3381: dirmngr won't start on Windows 10 with admin level account: T4264: Gpg4win 3.1.6.
Jan 24 2019, 7:32 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
aheinecke raised the priority of T3381: dirmngr won't start on Windows 10 with admin level account from Normal to High.

I want to have this fixed for the next release so prio high.

Jan 24 2019, 7:32 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
aheinecke assigned T3381: dirmngr won't start on Windows 10 with admin level account to werner.

Oops. Assignee removal was an accident. Sorry for the noise here ;-)

Jan 24 2019, 4:26 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
aheinecke placed T3381: dirmngr won't start on Windows 10 with admin level account up for grabs.

Just as a note: To workaround this you can also place "no-use-tor" into %APPDATA%\gnupg\dirmngr.conf (you might need to create that file) %APPDATA% expands to something like "c:\users\yourname\appdata\roaming"

Jan 24 2019, 4:25 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
Spiker added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

On Win 10 Pro it looks like File Transfer Server.exe is running on port 9050 which could be causing the issue. See screenshots.

That process is the one i killed which is part of Asus Wi-Fi Go

Jan 24 2019, 4:23 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
madhon added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

On Win 10 Pro it looks like File Transfer Server.exe is running on port 9050 which could be causing the issue. See screenshots.

Jan 24 2019, 4:20 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
Spiker added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

On Win 10 Pro it looks like File Transfer Server.exe is running on port 9050 which could be causing the issue. See screenshots.

Jan 24 2019, 4:16 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
madhon added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

Apparently i had a ASUS Wi-Fi go process listening on that port (even though i thought had uninstalled it), killing the process also allows dirmngr to start

Jan 24 2019, 3:34 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
aheinecke assigned T3381: dirmngr won't start on Windows 10 with admin level account to werner.

Thanks you very much for your help! I think we have it. \o/

Jan 24 2019, 3:23 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
madhon added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

Running with the --no-use-tor results in output ending with OK Dirmngr 2.2.11 at your service, attached is the procmon output , to clear up one thing q4master.idsoftware.com points to 127.0.0.1 in my hosts file (in addition to localhost also pointing to 127.0.0.1), but it seems the issue is with the tor check

Jan 24 2019, 3:07 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
aheinecke added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

I see some strangeness:
A TCP Connect: q4master.idsoftware.com:4862 -> q4master.idsoftware.com:9050
and TCP Send: q4master.idsoftware.com:4862 -> q4master.idsoftware.com:9050

Jan 24 2019, 2:58 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
madhon added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

Done, See attached

Jan 24 2019, 10:32 AM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report
aheinecke added a project to T3381: dirmngr won't start on Windows 10 with admin level account: gpg4win.

I'm thinking of how to move this forward.
The problem is that we (the developers) can't reproduce this at all and the debug output does not show anything.

Jan 24 2019, 9:04 AM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report

Jan 23 2019

Spiker added a comment to T3381: dirmngr won't start on Windows 10 with admin level account.

Has anybody discovered a fix for this issue? I'm running Win 10 Pro with Gpg4win v3.1.5. Dirmngr is still not executing and just hangs.

Jan 23 2019, 4:14 PM · libassuan, Testing, gpg4win, dirmngr, Windows, Bug Report

Dec 14 2018

wheelerlaw edited projects for T3065: dirmngr: proxy issues with dnslookup causing failure, added: gnupg (gpg22); removed FAQ.
Dec 14 2018, 7:29 PM · gnupg (gpg22), dns, dirmngr
wheelerlaw added a comment to T3065: dirmngr: proxy issues with dnslookup causing failure.
So if your DNS resolver does not tell us the IP addresses, we can't do anything about it.
Dec 14 2018, 7:25 PM · gnupg (gpg22), dns, dirmngr

Dec 11 2018

werner edited projects for T3065: dirmngr: proxy issues with dnslookup causing failure, added: FAQ; removed gnupg (gpg22).
Dec 11 2018, 3:48 PM · gnupg (gpg22), dns, dirmngr
werner added a comment to T3065: dirmngr: proxy issues with dnslookup causing failure.

If you specify a pool of keyservers dirmngr selects a keyserver on its won from the pool. This is so that it can use its own heuristics to detect whether a keyserver is dead and then retry another one. Now the default is a pool and your specified keyserver.ubuntu.com is also a pool (of two servers). So if your DNS resolver does not tell us the IP addresses, we can't do anything about it.

Dec 11 2018, 3:48 PM · gnupg (gpg22), dns, dirmngr
werner closed T4175: HTTP 5xx should fail over to the next server as Resolved.
Dec 11 2018, 3:05 PM · dirmngr, Feature Request
werner added a comment to T4175: HTTP 5xx should fail over to the next server.

Will go into 2.1.12 to be released next week.

Dec 11 2018, 3:05 PM · dirmngr, Feature Request
werner added a commit to T4175: HTTP 5xx should fail over to the next server: rGe5abdb6da7fa: dirmngr: Retry another server from the pool on 502, 503, 504..
Dec 11 2018, 1:41 PM · dirmngr, Feature Request
werner added a commit to T4175: HTTP 5xx should fail over to the next server: rG05ef62827844: dirmngr: Retry another server from the pool on 502, 503, 504..
Dec 11 2018, 1:40 PM · dirmngr, Feature Request
werner added a project to T3168: dirmngr: gpg: keyserver receive failed: No keyserver available: dns.
Dec 11 2018, 12:40 PM · dns, dirmngr
werner closed T3830: Dirmngr: Bad error message (regression) when no key is found on the keyserver as Resolved.

Thanks.

Dec 11 2018, 12:34 PM · gnupg, dirmngr
werner added a commit to T3830: Dirmngr: Bad error message (regression) when no key is found on the keyserver: rGf7ff25edadd4: gpg: In search-keys return "Not found" instead of "No Data"..
Dec 11 2018, 12:33 PM · gnupg, dirmngr
werner added a commit to T3830: Dirmngr: Bad error message (regression) when no key is found on the keyserver: rGe7252ae57f3c: gpg: In search-keys return "Not found" instead of "No Data"..
Dec 11 2018, 12:31 PM · gnupg, dirmngr

Nov 12 2018

aheinecke assigned T4249: No connection to Keyserver possible to werner.

I can reproduce it if I enter your or an unknown IP address.

Nov 12 2018, 10:25 AM · gnupg, dirmngr, Bug Report, gpg4win
aheinecke added a comment to T4182: Dirmngr: Keeps files in homedir open on Windows.

Mmh. It still makes a bit sense to me as I think it will be faster. But of course for memory mapped files the OS might decide.

Nov 12 2018, 9:18 AM · dirmngr

Nov 7 2018

werner added a comment to T4182: Dirmngr: Keeps files in homedir open on Windows.

The dirmngr may at any time open a file in that directory and thus there is no reliable way to remove the home directory when any gpg tool is running. Daemons need to be stopped before a directory can be deleted. So I think this is a non-issue and brought to the table only because we have that kludge of detecting a n unlinked directory on Unix. But even on Unix this is not possible to get rid of the home directory, for example if you want to umount it.

Nov 7 2018, 5:26 PM · dirmngr

Nov 6 2018

werner added a comment to T4175: HTTP 5xx should fail over to the next server.

Sorry, it didn't made it into 2.2.11.

Nov 6 2018, 12:48 PM · dirmngr, Feature Request

Nov 5 2018

werner edited projects for T3054: dirmngr only using cAcertificate attr type when querying LDAP directory, added: Active Directory; removed gnupg (gpg22).
Nov 5 2018, 9:33 AM · Active Directory, dirmngr
werner closed T3033: bug: dirmngr latches SRV port cross-scheme as Resolved.

No more complaints thus time to close.

Nov 5 2018, 9:30 AM · Testing, gnupg (gpg22), Bug Report, dirmngr