public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: JFLF <jflf-gitlab@outlook.com>
To: Florian Weimer <fweimer@redhat.com>,
	JFLF via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Un-deprecating nss_hesiod?
Date: Tue, 2 Mar 2021 21:13:29 +0100	[thread overview]
Message-ID: <AM0PR04MB7090F71175F3FC2D5F3F831D81999@AM0PR04MB7090.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <875z2bhzll.fsf@oldenburg.str.redhat.com>


Hi Florian,

Thank you for your answer.

On 01/03/2021 12.39, Florian Weimer wrote:
> * 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.

I might look into this at some point. Due to other commitments it won't
be at any time in the near future, though. Hopefully someone else will
step up before then.

Thanks!
JF

> Once that separate project exist, we can remove nss_hesiod from the
> glibc source tree.
> 
> Thanks,
> Florian
> 

  reply	other threads:[~2021-03-02 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 20:30 JFLF
2021-03-01 11:39 ` Florian Weimer
2021-03-02 20:13   ` JFLF [this message]
2021-03-04 14:55   ` Rich Felker
2021-03-04 16:34     ` Zack Weinberg

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=AM0PR04MB7090F71175F3FC2D5F3F831D81999@AM0PR04MB7090.eurprd04.prod.outlook.com \
    --to=jflf-gitlab@outlook.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).