From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: open issues
Date: Thu, 31 Aug 2017 11:34:05 +0200 [thread overview]
Message-ID: <20170831093405.GT15263@port70.net> (raw)
In-Reply-To: <CACOXvngft5Vy-gjbsdNNopVQq4CwJkbMUTx+KSQkY8-Qi=L=AA@mail.gmail.com>
* Stefan Sedich <stefan.sedich@gmail.com> [2017-08-30 19:53:55 +0000]:
> > feature request:
> > - RES_OPTIONS support for resolv.conf options overriding
> > http://www.openwall.com/lists/musl/2017/04/30/1
> > related libc-alpha discussion
> > http://sourceware.org/ml/libc-alpha/2017-08/msg01097.html
...
>
> - RES_OPTIONS support for resolv.conf options overriding
> http://www.openwall.com/lists/musl/2017/04/30/1
>
> I would love to sneak this one in if possible, has been sitting around for
> a while and something that I want to be able to configure!
did you see the libc-alpha discussion?
the current recommended way to override /etc/resolv.conf is using mount
namespace (or chroot), if user namespace is allowed for non-root users
in the kernel then this can be done without root access.
if you can control resolv.conf per process then options can be set too.
(not ideal solution, but may work for you)
next prev parent reply other threads:[~2017-08-31 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 4:36 Szabolcs Nagy
2017-08-27 6:07 ` A. Wilcox
2017-08-30 1:30 ` Rich Felker
2018-01-04 12:01 ` Alexander Monakov
2018-01-09 17:10 ` Rich Felker
2017-08-30 2:06 ` Rich Felker
2017-08-30 8:26 ` Pascal Cuoq
2017-08-30 19:20 ` Rich Felker
2017-08-30 19:37 ` Alexander Monakov
2017-08-30 20:10 ` Rich Felker
2017-08-30 19:51 ` A. Wilcox
2017-08-30 22:08 ` Rich Felker
2017-09-04 22:00 ` Szabolcs Nagy
2017-09-07 2:18 ` Rich Felker
2017-09-07 2:32 ` Rich Felker
2017-09-22 22:03 ` Szabolcs Nagy
2017-10-14 2:59 ` Rich Felker
2017-10-21 16:27 ` Rich Felker
2017-08-30 19:53 ` Stefan Sedich
2017-08-31 9:34 ` Szabolcs Nagy [this message]
2017-08-31 15:37 ` Stefan Sedich
2017-08-31 16:04 ` 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=20170831093405.GT15263@port70.net \
--to=nsz@port70.net \
--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).