From: Dax Kelson <Dax.Kelson@gurulabs.com>
To: trond.myklebust@fys.uio.no
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6]
Date: 12 Jan 2003 22:56:31 -0700 [thread overview]
Message-ID: <1042437391.1677.8.camel@thud> (raw)
In-Reply-To: <15906.1154.649765.791797@charged.uio.no>
On Sun, 2003-01-12 at 17:12, Trond Myklebust wrote:
> Hi Linus,
>
> The following set of 6 patches implements support for the RPCSEC_GSS
> security protocol (authentication only) and the Kerberos V5 security
> mechanism.
As a user and sysadmin, I've been waiting for this for a LONG time.
Standard NFS security/authentication sucks rocks. Without this NFS home
directory servers are just waiting to be ransacked by a rouge (or
compromised) root user on a client machine.
NFSv4 w/RPSEC_GSS is finally a native UNIX filesharing solution that I
don't have to be ashamed of when hanging with admins of those "other
OSes".
Dax
next prev parent reply other threads:[~2003-01-13 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 0:12 [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6] Trond Myklebust
2003-01-13 2:19 ` Jeff Garzik
2003-01-13 2:20 ` Jeff Garzik
2003-01-13 7:50 ` Trond Myklebust
[not found] ` <Pine.LNX.4.44.0301131556030.1095-100000@penguin.transmeta.com>
2003-01-14 15:24 ` [PATCH] Fix RPC client warning in 2.5.58 Trond Myklebust
2003-01-13 5:56 ` Dax Kelson [this message]
2003-01-13 7:49 ` [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6] Paul Jakma
2003-01-13 12:09 ` Trond Myklebust
2003-01-13 18:06 ` Dax Kelson
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=1042437391.1677.8.camel@thud \
--to=dax.kelson@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=torvalds@transmeta.com \
--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