From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 07F1B3896C12 for ; Mon, 1 Mar 2021 11:38:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 07F1B3896C12 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-309-PmOf8qC8NKS0Yhl6vVZ76Q-1; Mon, 01 Mar 2021 06:38:56 -0500 X-MC-Unique: PmOf8qC8NKS0Yhl6vVZ76Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BF22780196C; Mon, 1 Mar 2021 11:38:55 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-113-131.ams2.redhat.com [10.36.113.131]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EBF565C1C4; Mon, 1 Mar 2021 11:38:54 +0000 (UTC) From: Florian Weimer To: JFLF via Libc-alpha Cc: JFLF Subject: Re: Un-deprecating nss_hesiod? References: Date: Mon, 01 Mar 2021 12:39:50 +0100 In-Reply-To: (JFLF via Libc-alpha's message of "Thu, 25 Feb 2021 21:30:45 +0100") Message-ID: <875z2bhzll.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2021 11:39:00 -0000 * JFLF via Libc-alpha: > This is a very valid concern, but hasn't DNSSEC been implemented in > the glibc resolver in 2019? If so, doesn't that make this point moot? The glibc stub resolver is still non-validating. > So as long as it doesn't affect anything else, may I ask you to > consider un-deprecating nss_hesiod? NSS is a plug-in framework. There is no requirement that NSS service modules are built as part of glibc. Would you be interested in taking the nss_hesiod sources and maintaining them outside of the glibc source tree? Then nss_hesiod might even be able to reuse parts of the (already separate) hesiod library. Once that separate project exist, we can remove nss_hesiod from the glibc source tree. Thanks, Florian