From: Christoph Hellwig <hch@infradead.org>
To: Chris Siebenmann <cks@cs.toronto.edu>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
libc-alpha@sourceware.org
Subject: Re: Best approach for authenticating hosts for NFS (v3)?
Date: Wed, 5 Nov 2014 00:56:09 -0800 [thread overview]
Message-ID: <20141105085609.GA21735@infradead.org> (raw)
In-Reply-To: <20141104165313.CA9025A04C1@testapps.cs.toronto.edu>
On Tue, Nov 04, 2014 at 11:53:13AM -0500, Chris Siebenmann wrote:
> [*: Building a NSS module that supports netgroup lookups requires using
> an internal glibc header file to get a definition of a struct that
> is passed to NSS netgroup lookup functions.
It seems like that's where you should attack the problem. I've Cced the
glibc list to open the question if they really intended it to be a
private interface.
And even if they do using it anyway and dealign with the fact that you
have to be extremly careful with libc updates still sounds a lot less
painful than the other options.
next prev parent reply other threads:[~2014-11-05 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 16:53 Best approach for authenticating hosts for NFS (v3)? Chris Siebenmann
2014-11-05 8:56 ` Christoph Hellwig [this message]
2014-11-05 16:32 ` Steve Dickson
2014-11-05 16:45 ` Chris Siebenmann
2014-11-05 20:21 ` Steve Dickson
2014-11-09 20:50 ` Simo Sorce
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=20141105085609.GA21735@infradead.org \
--to=hch@infradead.org \
--cc=cks@cs.toronto.edu \
--cc=libc-alpha@sourceware.org \
--cc=linux-nfs@vger.kernel.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