From: bfields@fieldses.org (J. Bruce Fields)
To: Tamas Vincze <tom@vincze.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Varying ro/rw based on security flavor doesn't work
Date: Tue, 9 Jan 2018 14:23:38 -0500 [thread overview]
Message-ID: <20180109192338.GC18087@fieldses.org> (raw)
In-Reply-To: <890d00b1-fb64-1011-4a44-2e47713de0f7@vincze.org>
On Tue, Jan 09, 2018 at 10:11:05AM -0500, Tamas Vincze wrote:
> The exports man page says that one can vary ro/rw based on security
> flavor by including multiple sec= options in /etc/exports, but it
> seems to be broken in nfs-utils-1.3.0-0.48.el7_4.
>
> For example this /etc/exports:
>
> /export/pub 10.13.0.0/16(sec=sys,ro,sec=krb5i:krb5p,rw)
>
> results in this /var/lib/nfs/etab:
>
> /export/pub 10.13.0.0/16(rw,sync,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,anonuid=65534,anongid=65534,sec=sys,secure,root_squash,no_all_squash,sec=krb5i:krb5p,secure,root_squash,no_all_squash)
>
> Only the rw option is present in etab, that applies to both sec=sys
> and sec=krb5i:krb5p.
>
> Is this bug specific to redhat or also present upstream?
I don't know off the top of my head.... Is there a redhat bug filed?
And is there some prevoius version that you know worked?
Agreed that it looks like a bug.
--b.
next prev parent reply other threads:[~2018-01-09 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 15:11 Varying ro/rw based on security flavor doesn't work Tamas Vincze
2018-01-09 19:23 ` J. Bruce Fields [this message]
2018-01-09 20:47 ` Tamas Vincze
2018-01-11 15:36 ` Tamas Vincze
2018-01-11 18:11 ` Justin Mitchell
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=20180109192338.GC18087@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tom@vincze.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