From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: resolv.conf and gnupg2
Date: Mon, 8 Aug 2022 13:50:19 +0200 [thread overview]
Message-ID: <YvD4eyWESSm9rUpo@calimero.vinschen.de> (raw)
In-Reply-To: <871qtrayfl.fsf@Otto.invalid>
On Aug 8 11:15, ASSI wrote:
> Mark Geisert writes:
> > Could Cygwin itself provide a minimal /etc/resolv.conf pointing to
> > public DNS server(s)? Some users might object to Google's public DNS
> > (e.g. 8.8.8.8) though.
>
> No, this would be the job for any software that configures the DNS
> resolver. However, I'd prefer if no resolver libraries ever looked at
> /etc/resolv.conf as it doesn't really make sense for Cygwin to muck
> about with the DNS configuration independently of what Windows provides.
I agree, actually.
Right now, Cygwin's resolver checks for /etc/resolv.conf, too, but uses
the OS stuff if /etc/resolv.conf isn't available.
So I wonder, just as you do, if we shouldn't drop support for
/etc/resolv.conf and let this be handled by the OS only.
In theory, we have two scenarios:
- Either a user is also admin and can change the OS settings anyway,
- or the user is not admin and the admins very likely don't like the
user to change the resolver settings on the company machine...
Corinna
next prev parent reply other threads:[~2022-08-08 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 14:34 Marco Atzeri
2022-08-07 22:33 ` Mark Geisert
2022-08-08 9:15 ` ASSI
2022-08-08 11:50 ` Corinna Vinschen [this message]
2022-08-08 7:30 ` Corinna Vinschen
2022-08-08 11:54 ` Corinna Vinschen
2022-08-08 12:13 ` Yasuhiro Kimura
2022-08-08 14:13 ` Corinna Vinschen
2022-08-08 18:29 ` Chad Dougherty
2022-08-10 17:22 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvD4eyWESSm9rUpo@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).