From: Stefan Sedich <stefan.sedich@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Add RES_OPTIONS support for resolv.conf options overriding
Date: Tue, 25 Apr 2017 04:30:58 +0000 [thread overview]
Message-ID: <CACOXvniOKm4iB7M7LVs=U58w+ER_Kfj9mo_A5sXNTgN3L=H2vg@mail.gmail.com> (raw)
In-Reply-To: <20170425025043.GF27654@wopr>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Rich,
I will make the change, but so I understand some more what would be the
implications of not ignoring it in this scenario? I understand why it is
bad in the case of the load paths for example but just want to understand
the issue in this context.
- Stefan
On Mon, Apr 24, 2017 at 7:50 PM Kurt H Maier <khm@sdf.org> wrote:
> On Mon, Apr 24, 2017 at 10:39:34PM -0400, Rich Felker wrote:
> >
> > What I'd really like is a way for users to override nameserver and
> > search directives (so pretty much, all of resolv.conf) in a way that
> > doesn't need root; this would be really valuable for testing. But
> > sadly there's no precedent for an interface to do so. Maybe it's
> > something we could work on a unified solution to with other
> > implementations (glibc, bsds?).
> >
> > Rich
>
> FreeBSD and OpenBSD both currently support RES_OPTIONS (and LOCALDOMAIN
> for overriding the search directive) but I don't think they support
> overriding the nameserver directive. There's just the HOSTALIASES
> variable for pointing to a file full of 'alias hostname' pairs.
>
> khm
>
[-- Attachment #2: Type: text/html, Size: 1507 bytes --]
next prev parent reply other threads:[~2017-04-25 4:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 2:21 Stefan Sedich
2017-04-25 2:39 ` Rich Felker
2017-04-25 2:50 ` Kurt H Maier
2017-04-25 4:30 ` Stefan Sedich [this message]
2017-04-25 16:48 ` Rich Felker
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='CACOXvniOKm4iB7M7LVs=U58w+ER_Kfj9mo_A5sXNTgN3L=H2vg@mail.gmail.com' \
--to=stefan.sedich@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).