From: "J. Bruce Fields" <bfields@fieldses.org>
To: Thanos Chatziathanassiou <tchatzi-nz9JlX+3IF8@public.gmane.org>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils-1.1.6 released.
Date: Tue, 28 Apr 2009 11:29:18 -0400 [thread overview]
Message-ID: <20090428152918.GF17891@fieldses.org> (raw)
In-Reply-To: <49F71D66.4070204-nz9JlX+3IF8@public.gmane.org>
On Tue, Apr 28, 2009 at 06:14:46PM +0300, Thanos Chatziathanassiou wrote:
> I already did and attached it as nfs.pkt before. Is it missing something ?
Whoops, sorry, wasn't paying attention.
So, yes, if you look at the "Remote Procedure Call"->"Credentials" on
the next-to-last packet (#25), you'll see that it's sending the CREATE
with AUTH_NULL credentials field.
So the create's going to be done with nfsnobody credentials, and won't
succeed unless it's in a world-writeable directory.
The mount reply (packet #10) is listing the flavors as: AUTH_NULL,
AUTH_UNIX, RPCSEC_GSS_KRB5, RPCSEC_GSS_KRB5I, RPCSEC_GSS_KRB5P in that
order. The client may just be choosing the first?
I seem to recall a couple bugs in this area that were fixed recently,
but can't find those now.
--b.
next prev parent reply other threads:[~2009-04-28 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 18:07 nfs-utils-1.1.6 released Steve Dickson
[not found] ` <49ECB9E6.4010001-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-04-21 17:10 ` Thanos Chatziathanassiou
[not found] ` <49EDFE21.2000007-nz9JlX+3IF8@public.gmane.org>
2009-04-22 15:40 ` Steve Dickson
[not found] ` <49EF3A83.50409-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-04-22 15:54 ` J. Bruce Fields
2009-04-28 11:34 ` Thanos Chatziathanassiou
[not found] ` <49F6E9B3.2090508-nz9JlX+3IF8@public.gmane.org>
2009-04-28 15:05 ` J. Bruce Fields
2009-04-28 15:14 ` Thanos Chatziathanassiou
[not found] ` <49F71D66.4070204-nz9JlX+3IF8@public.gmane.org>
2009-04-28 15:29 ` J. Bruce Fields [this message]
2009-04-28 15:23 ` Chuck Lever
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=20090428152918.GF17891@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tchatzi-nz9JlX+3IF8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.