public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pemensik at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/24255] resolver should handle special domains correctly
Date: Mon, 12 Jun 2023 14:15:55 +0000	[thread overview]
Message-ID: <bug-24255-131-FSX7fWSEHN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24255-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24255

--- Comment #3 from Petr Menšík <pemensik at redhat dot com> ---
I do not think we ever want to override output of files database. If the user
defines his own example.onion name in /etc/hosts, then he should receive it in
queries. He wants it and we should not filter his wishes.

And for DNS, we cannot know if that the server is connected to Tor or not. I
guess we could block DNS query if the server were not sent to ::1 or
127.0.0.0/8. But handling this at dns plugin seems wrong to me. And it should
be possible to configure it for unusual setups, where we want it forwarded
anyway.

I think system services like Network Manager or systemd-networkd would be
better suited to decide whether such queries should be forwarded or discarded
on low level. Perhaps Tor service could remove onion domain from blocked list
on startup and return it when shut down.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-06-12 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24255-131@http.sourceware.org/bugzilla/>
2023-06-12 13:32 ` pemensik at redhat dot com
2023-06-12 13:55 ` crrodriguez at opensuse dot org
2023-06-12 14:15 ` pemensik at redhat dot com [this message]
2024-02-24  8:00 ` milahu at gmail dot com

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=bug-24255-131-FSX7fWSEHN@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).