From: steve <steve@steve-ss.com>
To: tigran.mkrtchyan@desy.de
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs4 keytabs [was:Re: where can I ask user qns about nfs4]?
Date: Thu, 02 Feb 2012 15:56:48 +0100 [thread overview]
Message-ID: <4F2AA430.2040109@steve-ss.com> (raw)
In-Reply-To: <4F2A8FBC.1010101@steve-ss.com>
On 02/02/12 14:29, steve wrote:
> On 02/02/2012 02:05 PM, Tigran Mkrtchyan wrote:
>> On Thu, Feb 2, 2012 at 12:33 PM, steve<steve@steve-ss.com> wrote:
>>> On 02/02/12 11:58, Tigran Mkrtchyan wrote:
>>>> Hi Steve,
>>>>
>>>>> I already use nfs4 to serve my Linux clients. I'm going to
>>>>> kerberize it.
>>>>> My
>>>>> clients already have machine and host principals. What else do
>>>>> they need?
>>>>>
>>>>> 1. nfs/client.domain.name
>>>>> 2. nfs/server.domain/name
>>>>> 3. neither
>>>>> 4. both
>>>>>
>>>> We run kerberized NFS.
>>>>
>>>> our keytab contains:
>>>>
>>>> on server;
>>>> nfs/server.domain
>>>>
>>>> on client:
>>>> nfs/client.domain
>>>>
>>>> and, of course, you need a consistent idmap configuration.
>>>>
>>>> Tigran.
>>>>
>>> Hi Tigran
>>>
>>> That's what we have on our test lan at the moment. I can understand
>>> that the
>>> server would need the service principal:
>>> nfs/server.domain
>>> but not the client, as it's not offering any kerberized service.
>> The mount step happens on behalf of host as there are no user
>> requests yet.
>> Client host credentials are used at that time.
>>
>>> As an experiment, I removed the nfs/client.domain from a client keytab,
>>> rebooted and remounted the share. We could still access the
>>> kerberized nfs
>>> share. Maybe there were still some tickets left somewhere? That has me
>>> really confused.
>> Huh! did you enforce kerberos in /etc/exports?
>>
> Yes. /etc/exports exports as gss/krb5
> I made a screenshot:
>
> http://3.bp.blogspot.com/-g40b11Ys_DA/TypYtlO-ixI/AAAAAAAAAIc/cZdeRhnVuY4/s1600/s4all.png
>
>
> That's why I'm confused.
> Steve
Digging a bit further, here is the output of mount on the client:
http://dl.dropbox.com/u/45150875/krb5testnfs.png
And this appears immediately after the mount:
http://dl.dropbox.com/u/45150875/krb5nfstmp.png
Most of the documentation tells you to stick nfs into the client keytab
as well as the server keytab, but here, I only have the principal on the
server.
What am I missing?
Thanks,
Steve
next prev parent reply other threads:[~2012-02-02 14:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 6:39 where can I ask user qns about nfs4? steve
2012-02-02 10:58 ` Tigran Mkrtchyan
2012-02-02 11:33 ` nfs4 keytabs [was:Re: where can I ask user qns about nfs4]? steve
2012-02-02 13:05 ` Tigran Mkrtchyan
2012-02-02 13:29 ` steve
2012-02-02 14:56 ` steve [this message]
2012-02-02 18:57 ` Tigran Mkrtchyan
2012-02-03 17:22 ` steve
2012-02-06 13:31 ` steve
2012-02-04 20:50 ` where can I ask user qns about nfs4? Liam Gretton
2012-02-05 9:26 ` steve
2012-02-05 14:16 ` Jim Rees
2012-02-05 16:55 ` Liam Gretton
2012-02-05 17:37 ` Jim Rees
2012-02-06 16:39 ` J. Bruce Fields
2012-02-06 18:54 ` steve
2012-02-09 18:57 ` Don Riden
2012-02-09 19:33 ` steve
2012-02-10 8:19 ` steve
2012-02-10 18:40 ` J. Bruce Fields
2012-02-10 19:13 ` steve
2012-02-10 19:14 ` J. Bruce Fields
2012-02-10 23:20 ` steve
2012-02-10 20:47 ` Liam Gretton
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=4F2AA430.2040109@steve-ss.com \
--to=steve@steve-ss.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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 NNTP newsgroup(s).