From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EF5913858D32; Mon, 12 Jun 2023 13:55:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF5913858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1686578135; bh=c5dH3yO0htV+J4cclPrv4fXKf1pdM6iBm+6pD6xqnuc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QEIMqP3136IVc4PpbPSGfcjwlK7/WmBKPPhF460Wwmq9CfZ90//nJX95syulUp2xU RmEpwqCpNq+IVfk9v2OB1ARxRm+jVuXXmuRKcVQYLCDdOFTJDavxsWeGN9vA0ZS/uy lIWKOs1FtnlTd1JdSxszmJfpqdlapyp6Vj1M8GFE= From: "crrodriguez at opensuse dot org" To: glibc-bugs@sourceware.org Subject: [Bug network/24255] resolver should handle special domains correctly Date: Mon, 12 Jun 2023 13:55:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: network X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: crrodriguez at opensuse dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D24255 --- Comment #2 from Cristian Rodr=C3=ADguez --- (In reply to Petr Men=C5=A1=C3=ADk from comment #1) > 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 i= nto > TOR network to appropriate DNS servers. >=20 > 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 forwardi= ng > it to upstream DNS servers. That is what we want. It either handles it or > blocks it. >=20 > I don't think this can be decided by glibc, it is not aware of configurat= ion > 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. This is not what the relevant standards say though. " 3. Name Resolution APIs and Libraries: Resolvers MUST either respond to requests for .onion names by resolving them according to [tor-rendezvous] or by responding with NXDOMAIN [RFC1035]." glibc does not know and will probably never know by itself how to tor-rendezvous, it could of course do it using an nss-module which must come before dns or files in /etc/nsswitch.conf ..but the dns and files module mu= st return NXDOMAIN on such names. --=20 You are receiving this mail because: You are on the CC list for the bug.=