From: "mfulz" <mfulz@olznet.de>
To: "Florian Weimer" <fweimer@redhat.com>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: Idea / Patch to add very simple uid filtering to resolv.conf
Date: Tue, 12 Sep 2023 15:34:54 +0000 [thread overview]
Message-ID: <kcEE.4pM8LWTUQmKCTD9WIGLyuA.AKNQrY7l2QE@boink> (raw)
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
It's complexity we'd have to maintain.
Valid point and if there is no use for anyone totally ok.
But the point for a service is that I'd basically have to keep a fork of libresolv and nss_dns up2date for this change which is much more work.
That's the reason why I was asking, perhaps some others would see some need for it.
It also breaks in case processes
switch to some other for increased isolation (perhaps with user
namespaces).
Therefore I wanted to keep the legacy behavior untouched.
If there is no need to use uid filters just dig with the used config without any changes.
I recommend the separate service module approach.
If I have to do it that way sure.
Perhaps someone can give me some hints if there is a easier way to go for it instead of cloning the whole nss_dns including libresolv?
next reply other threads:[~2023-09-12 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 15:34 mfulz [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-12 12:25 Matthias Fulz
2023-09-12 14:50 ` Florian Weimer
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=kcEE.4pM8LWTUQmKCTD9WIGLyuA.AKNQrY7l2QE@boink \
--to=mfulz@olznet.de \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
/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).