Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "François Valenduc" <francois.valenduc@skynet.be>
Cc: Kevin Coffman <kwc@umich.edu>, linux-nfs@vger.kernel.org
Subject: Re: nfs and kerberos authentification problem.
Date: Fri, 5 Sep 2008 17:26:43 -0400	[thread overview]
Message-ID: <20080905212643.GG12947@fieldses.org> (raw)
In-Reply-To: <48C1810C.5090703@skynet.be>

On Fri, Sep 05, 2008 at 08:57:16PM +0200, Fran=C3=A7ois Valenduc wrote:
> What I don' understand is that the file system is well mounted read-w=
rite:
> pc-francois:/home/francois on /mnt/pc-francois type nfs =20
> (rw,users,noatime,sec=3Dkrb5,rsize=3D1024,wsize=3D1024,soft,addr=3D19=
2.168.1.2)
>
> The mounted directory has the following permissions:
>
> drwxrwsr-x 77 francois francois 4,0K sep  5 20:35 pc-francois/
>
> So, I don't understand why I can't write any file on it.

The way it would normally work is you'd have a kerberos principal named
"francois-wmZDWbG+120CDknkFGB/9A@public.gmane.org", and you'd run

	kinit francois-wmZDWbG+120CDknkFGB/9A@public.gmane.org

(or that'd be done automatically for you on login if you have the right
pam setup).  When you do an nfs operation then the server will see you
as francois-wmZDWbG+120CDknkFGB/9A@public.gmane.org, look for a local user named "francois", an=
d
use that uid/gid.

But all authentication in nfs is per-user, not per-client, so you need =
a
krb5 principal for each user.

--b.

  reply	other threads:[~2008-09-05 21:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 18:19 nfs and kerberos authentification problem François Valenduc
2008-09-03 20:12 ` Kevin Coffman
     [not found]   ` <4d569c330809031312p3515f4d8id9cbec94d871e058-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-04 16:45     ` François Valenduc
2008-09-04 16:56       ` J. Bruce Fields
2008-09-04 17:31         ` François Valenduc
2008-09-04 17:33           ` J. Bruce Fields
2008-09-04 17:41             ` François Valenduc
2008-09-04 17:49               ` J. Bruce Fields
2008-09-04 17:58                 ` François Valenduc
2008-09-04 18:39                   ` J. Bruce Fields
2008-09-04 18:53                     ` François Valenduc
2008-09-04 18:59                       ` J. Bruce Fields
2008-09-04 19:31                         ` Kevin Coffman
     [not found]                           ` <4d569c330809041231wcbddde8w419968280de9e39a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-04 19:38                             ` François Valenduc
2008-09-04 19:40                               ` J. Bruce Fields
2008-09-04 19:41                                 ` J. Bruce Fields
2008-09-04 19:56                                   ` François Valenduc
2008-09-05 18:36                                 ` François Valenduc
2008-09-05 18:57                                   ` François Valenduc
2008-09-05 21:26                                     ` J. Bruce Fields [this message]
2008-09-05 21:23                                   ` J. Bruce Fields

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=20080905212643.GG12947@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=francois.valenduc@skynet.be \
    --cc=kwc@umich.edu \
    --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