From: Jeff Garzik <jgarzik@pobox.com>
To: Trond Myklebust <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: Sun, 12 Jan 2003 21:19:51 -0500 [thread overview]
Message-ID: <20030113021951.GE18756@gtf.org> (raw)
In-Reply-To: <15906.1154.649765.791797@charged.uio.no>
On Mon, Jan 13, 2003 at 01:12:50AM +0100, Trond Myklebust wrote:
> Our wish is to provide basic kernel RPC client support for the generic
> RPCSEC_GSS protocol, and for communicating with a userland daemon that
> does the actual the security context negotiation with the RPC server.
> Communication between kernel and userland is done over a set of named
> pipes (in much the same way as the CODA upcall/downcall is done) in a
> private ramfs-like filesystem.
Well, AFS also wants Kerb [but a weird Kerb4 variant IIRC], but,
OTOH why not do all this authentication and stuff in userspace?
Several other projects through the years have done similar things, where
a userspace daemon handles auth and such, and then passes an fd into
the kernel via ioctl [or write(2)ing fd value to a mini-ramfs VFS node].
next prev parent reply other threads:[~2003-01-13 2:11 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 [this message]
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 ` [PATCH] Secure user authentication for NFS using RPCSEC_GSS [0/6] Dax Kelson
2003-01-13 7:49 ` 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=20030113021951.GE18756@gtf.org \
--to=jgarzik@pobox.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