From: Jaap Winius <jwinius@umrk.nl>
To: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 cross-realm support
Date: Mon, 7 Jul 2014 16:23:17 +0000 (UTC) [thread overview]
Message-ID: <lpehhl$o74$1@ger.gmane.org> (raw)
In-Reply-To: CAHVgHyVjoVb--cfbaopoUYA4vbDCjufJVng6OM2e82q0yEMthA@mail.gmail.com
On Mon, 07 Jul 2014 08:36:00 -0400, Andy Adamson wrote:
> So you are supporting two Kerberos realms under one NFSv4 domain?
At some point I even hope to make it three Kerberos realms under one
NFSv4 domain, but this also depends on a cross-realm issue with Exim4
being resolved, so for now it's just two realms under one NFSv4 domain.
> You are using LDAP for id mapping?
Yes. After tweaking the user-olcAuthzRegexp for cn=config it seems to be
working perfectly.
> Which version of nfs-utils and which client kernel?
I'm using Debian wheezy (stable), which comes with with nfs-common
1.2.6-4 and kernel 3.2.0-4-amd64.
Cheers,
Jaap
next prev parent reply other threads:[~2014-07-07 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 17:42 NFSv4 cross-realm support Jaap Winius
2014-07-07 12:36 ` Andy Adamson
2014-07-07 16:23 ` Jaap Winius [this message]
2014-07-07 21:24 ` Andy Adamson
2014-07-08 1:33 ` Jaap Winius
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='lpehhl$o74$1@ger.gmane.org' \
--to=jwinius@umrk.nl \
--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