From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: [TUHS] NFS & Kerberos woes...
Date: Tue, 25 Dec 2018 17:49:49 -0700 [thread overview]
Message-ID: <bd626b01-b74a-14d9-c31e-6b5437464387@spamtrap.tnetconsulting.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
Do any fellow TUHS subscribers have any experience with NFS,
particularly in combination with Kerberos authentication?
I'm messing with something that is making me think that Kerberos
authentication (sec=krb5{,i,p}) usurps no_root_squash.
Meaning that root can't access files owned by other users with go-rwx.
Almost as if no_root_squash wasn't configured on the export.
Does anyone have a spare bone that they would be willing to throw my way?
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4008 bytes --]
next reply other threads:[~2018-12-26 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 0:49 Grant Taylor via TUHS [this message]
2018-12-26 2:01 ` Larry McVoy
2018-12-26 4:49 ` Theodore Y. Ts'o
2018-12-26 8:45 ` Grant Taylor via TUHS
2018-12-27 6:27 ` Grant Taylor via TUHS
2018-12-26 8:48 ` Grant Taylor via TUHS
2018-12-27 6:24 ` [TUHS] NFS & Kerberos woes... — SOLVED Grant Taylor via TUHS
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=bd626b01-b74a-14d9-c31e-6b5437464387@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).