Linux NFS development
 help / color / mirror / Atom feed
From: Orion Poplawski <orion@nwra.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Trouble with multiple kerberos ticket caches
Date: Fri, 2 May 2025 11:29:58 -0600	[thread overview]
Message-ID: <c4ecc067-9a51-40c8-9300-29119ff2e1d0@nwra.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

One of our users is struggling with multiple kerberos ticket caches impacting
access to NFS sec=krb5 mounts.

Because home directories are NFS mounted, we use GSSAPI auth to forward a
ticket.  But then we need to kinit to have a long-term renewable ticket.

But we seem to be seeing that new ssh connections which create a new ticket
cache break access to the NFS mounts, resulting in "permission denied" or
"Stale file handle" messages.  Switching back to a renewable ticket cache
seems to resolve the issue.

Any suggestions?  Is this expected?  I would have thought that the nfs access
would work with any valid ticket.

NAME="AlmaLinux"
VERSION="8.10 (Cerulean Leopard)"
nfs-utils-2.3.3-59.el8.x86_64
4.18.0-553.50.1.el8_10.x86_64

-- 
Orion Poplawski
he/him/his  - surely the least important thing about me
Manager of IT Systems                      720-772-5637
NWRA, Boulder Office                  FAX: 303-415-9702
3380 Mitchell Lane                       orion@nwra.com
Boulder, CO 80301                 https://www.nwra.com/


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4087 bytes --]

             reply	other threads:[~2025-05-02 17:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 17:29 Orion Poplawski [this message]
2025-05-06 19:54 ` Trouble with multiple kerberos ticket caches Orion Poplawski
2025-05-07 16:57   ` Daniel Kobras
2025-05-07 17:39     ` Orion Poplawski
2025-05-09 13:21       ` Daniel Kobras
2025-05-09 19:55         ` Trouble with kerberos encryption types Orion Poplawski
2025-05-09 21:03           ` Orion Poplawski
2025-05-12 15:46             ` Daniel Kobras

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=c4ecc067-9a51-40c8-9300-29119ff2e1d0@nwra.com \
    --to=orion@nwra.com \
    --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