Re: resolv.conf and gnupg2

[Yasuhiro Kimura <yasu@utahime.org>]

From: Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: Re: resolv.conf and gnupg2
Date: Mon, 8 Aug 2022 09:30:47 +0200

> I can't believe (but may be wrong, of course) that gnupg2 tries to
> access /etc/resolv.conf by itself.  I would rather guess that gnupg2
> is linked against one or more libs provided by the bind package,
> and thus uses the resolver from the bind package.  However, Cygwin
> provides its own resolver entry points, and those don't need
> /etc/resolv.conf, because they utilize the OS resolver.
> 
> Is there a build option to avoid building against the bind lib?
> Alternatively it might be possible to inject an autoconf variable
> from cygport...?
> 
> 
> Corinna

Unfortunately it seems gnupg2 accesses /etc/resolv.conf in some way.

(Cygwin64)yasu@rolling[1007]% pwd
/cygdrive/c/Users/yasu/Work/gnupg
(Cygwin64)yasu@rolling[1008]% git grep -F resolv.conf
NEWS:  * dirmngr: Make reading resolv.conf more robust.  [T5657]
NEWS:  * dirmngr: Now detects a changed /etc/resolv.conf.
dirmngr/dns-stuff.c:#define RESOLV_CONF_NAME "/etc/resolv.conf"
dirmngr/dns-stuff.c:  /* Force a reload if resolv.conf has changed.  */
dirmngr/dns-stuff.c:        log_debug ("dns: resolv.conf changed - forcing reload\n");
dirmngr/dns.c:  if ((error = dns_resconf_loadpath(resconf, "/etc/resolv.conf"))) {
dirmngr/dns.c:           * /etc/resolv.conf, defaulting to a nameserver of
dirmngr/dns.c:/** ugly hack to support specifying ports other than 53 in resolv.conf. */
dirmngr/dns.c:           * is the intersection of the /etc/resolv.conf families and
dirmngr/dns.c:           * /etc/resolv.conf has "family inet4" and .ai_type
dirmngr/dns.c:          MAIN.resconf.path[MAIN.resconf.count++] = "/etc/resolv.conf";
dirmngr/dns.c:  { "show-resconf",       &show_resconf,          "show resolv.conf data" },
dirmngr/dns.c:          "  -c PATH   Path to resolv.conf\n"
(Cygwin64)yasu@rolling[1009]%

---
Yasuhiro Kimura