public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "milahu at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/24255] resolver should handle special domains correctly Date: Sat, 24 Feb 2024 08:00:09 +0000 [thread overview] Message-ID: <bug-24255-131-fkP42BsYBA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24255-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24255 milahu <milahu at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |milahu at gmail dot com --- Comment #4 from milahu <milahu at gmail dot com> --- > for DNS, we cannot know if that the server is connected to Tor or not imo, the optimal solution would be to extend /etc/resolv.conf with something like > option allow-domains *.onion ... to make tools like curl and git "just work" on machines behind a transparent tor proxy where these tools currently throw the error > Not resolving .onion address (RFC 7686) ... and currently we need non-transparent workarounds like > curl --proxy socks5h://127.0.0.1:9050 > git -c remote.origin.proxy=socks5h://127.0.0.1:9050 ... or expensive workarounds like "rebuild curl" which on systems like nixos or guix means "rebuild the world" this config belongs to /etc/resolv.conf because its a machine-level config which affects all DNS clients on that machine the default config would be something like > option deny-domains *.onion *.i2p see also https://github.com/curl/curl/discussions/11125 I want to resolve onion addresses https://gitlab.torproject.org/tpo/core/torspec/-/issues/202 Formalize toggle override for non-Tor applications that follow RFC 7686 -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-24 8:00 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 2024-02-24 8:00 ` milahu at gmail dot com [this message]
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-fkP42BsYBA@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).