From: Zhang Weiwu <zhangweiwu@realss.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: when will we be able to use LIPKEY on NFS4 on Linux?
Date: Mon, 27 Sep 2010 23:01:49 +0800 [thread overview]
Message-ID: <4CA0B1DD.1000605@realss.com> (raw)
In-Reply-To: <1285590266.19362.37.camel@heimdal.trondhjem.org>
On 2010年09月27日 20:24, Trond Myklebust wrote:
>
> We're likely to drop the requirement that SPKM3/LIPKEY ...
> SPKM3 mechanism (on which LIPKEY relies) appears
> to contain inherent security flaws that are difficult to fix.
Thanks for the clear answer. We have a few setups where an
infrastructure is close to not possible (Kerberos) thus at the moment we
are deciding between switching to samba for username/password
authentication from NFS or uses the long-expected LIPKEY. samba might
have other inherent security flaws but practically security is not a
priority of our concern at the moment. Your information is directly
helpful for making a decision:) thanks!
prev parent reply other threads:[~2010-09-27 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 8:35 when will we be able to use LIPKEY on NFS4 on Linux? Zhang Weiwu
2010-09-27 12:24 ` Trond Myklebust
2010-09-27 15:01 ` Zhang Weiwu [this message]
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=4CA0B1DD.1000605@realss.com \
--to=zhangweiwu@realss.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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