From: Ralph Zack <ralphz@zoho.com>
To: linux-nfs@vger.kernel.org
Subject: Re: Secure NFSv4 mounts and daemons
Date: Sat, 17 Jan 2015 12:53:40 +0100 [thread overview]
Message-ID: <54BA4D44.9060303@zoho.com> (raw)
In-Reply-To: <alpine.OSX.2.19.9992.1501161628010.498@planck.local>
On 01/16/2015 10:36 PM, Benjamin Coddington wrote:
> Wow, looks like kinit /will/ read your password from stdin. I had no idea.
>
> I've done this with a keytab and cron job running as the
> service's user to keep the credential caches for the service's user fresh.
> Kinit should be something like `kinit -kt /keyab/file batch/host@realm.com`
> Run your jobs more frequently than the ticket expiry time and everything
> should be fine.
That is pretty much what I had in mind if there was no better solution.
It just seemed bit hacky to me and I thought there was maybe a more
elegant solution, but I may end up doing it like that.
On 01/17/2015 12:11 AM, Anthony Messina wrote:
> I use GSS-Proxy for this:
> https://fedorahosted.org/gss-proxy/
>
That looks very interesting at first glance, I'll have a closer look at
it. Thanks!
- Ralph
next prev parent reply other threads:[~2015-01-17 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:12 Secure NFSv4 mounts and daemons Ralph Zack
2015-01-16 9:06 ` Paul van der Vlis
2015-01-16 21:36 ` Benjamin Coddington
2015-01-17 11:53 ` Ralph Zack [this message]
2015-01-16 23:11 ` Anthony Messina
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=54BA4D44.9060303@zoho.com \
--to=ralphz@zoho.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