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 13:32:10 +0000 [thread overview] Message-ID: <bug-24255-131-2SGMJ38fou@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24255-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24255 Petr Menšík <pemensik at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pemensik at redhat dot com --- Comment #1 from Petr Menšík <pemensik at redhat dot com> --- I do not think this is a good idea. If one is running a local cache on his machine, he might be able to forward onion. zone and all requests to it into TOR network to appropriate DNS servers. That would be no longer possible if glibc blocked that query from DNS. I think we want it blocked only from forwarding to 3rd party servers. For example unbound or bind will create empty zones for it, blocking forwarding it to upstream DNS servers. That is what we want. It either handles it or blocks it. I don't think this can be decided by glibc, it is not aware of configuration details of DNS. I would instead propose to have optional NSS hosts plugin with configurable blocklist, which could be put before dns in /etc/nsswitch.conf. If you would include onion in it, it would authoritatively say does not exist without allowing that in DNS. If you would have local dns cache able to configure this properly, it would not use such module. -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2023-06-12 13:32 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 [this message] 2023-06-12 13:55 ` crrodriguez at opensuse dot org 2023-06-12 14:15 ` pemensik at redhat dot com 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-2SGMJ38fou@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: linkBe 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).