public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Matthias Fulz <mfulz@olznet.de>
Cc: libc-help@sourceware.org
Subject: Re: Idea / Patch to add very simple uid filtering to resolv.conf
Date: Tue, 12 Sep 2023 16:50:02 +0200	[thread overview]
Message-ID: <87r0n35tut.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <2a1c4925-7ad4-4673-9954-72d556d0b8f1@olznet.de> (Matthias Fulz's message of "Tue, 12 Sep 2023 14:25:16 +0200")

* Matthias Fulz:

> Further if the uid is not added to the line the behavior would be the
> same as it was before the patch.
> Would be nice if this could be included, or at least please explain
> why not for my understanding as I can't see any reason that would be
> against it

It's complexity we'd have to maintain.  It also breaks in case processes
switch to some other for increased isolation (perhaps with user
namespaces).

I recommend the separate service module approach.

Thanks,
Florian


  reply	other threads:[~2023-09-12 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 12:25 Matthias Fulz
2023-09-12 14:50 ` Florian Weimer [this message]
2023-09-12 15:34 mfulz

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=87r0n35tut.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=mfulz@olznet.de \
    /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).