From: Charles Hedrick <hedrick@rutgers.edu>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: can gssproxy be used for both cron jobs and normal users?
Date: Wed, 8 Oct 2025 18:02:34 +0000 [thread overview]
Message-ID: <a4a13129-a50c-4ecd-b323-dfcb4066af5c@cs.rutgers.edu> (raw)
My apologies for the previous copy. That was Microsoft's idea of plain
text. This is Thunderbird's.
-----------------------------
About a month ago there was discussion about gssproxy, including use for
cron jobs.
I just did some testing. With constrained delegation I can make cron
jobs work. However when I do, normal users can no longer use NFS. It
appears that when rpc.gssd has GSS_USE_PROXY set, it always uses the
proxy. So normal Kerberos tickets from login or ssh don't work. I looked
at the source for gssproxy. It appears that when impersonation is turned
on, it always tries to impersonate. It doesn't check if there's a
TGT that would allow it to get a normal service ticket.
next reply other threads:[~2025-10-08 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 18:02 Charles Hedrick [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-09 19:59 can gssproxy be used for both cron jobs and normal users? Charles Hedrick
2025-10-08 17:09 Charles Hedrick
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=a4a13129-a50c-4ecd-b323-dfcb4066af5c@cs.rutgers.edu \
--to=hedrick@rutgers.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;
as well as URLs for NNTP newsgroup(s).