From: Per Olofsson <pelle@dsv.su.se>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Paul Jakma <paul@clubi.ie>,
nfs@lists.sourceforge.net
Subject: Re: NFSv3+Krb5 and mountd
Date: Mon, 30 Aug 2004 23:25:33 +0200 [thread overview]
Message-ID: <20040830212533.GN3671@nasse> (raw)
In-Reply-To: <1093884302.8729.21.camel@lade.trondhjem.org>
Trond Myklebust:
> This is already implemented...
>
> The RPCSEC_GSS implementation that is in linux-2.6.x already follows the
> guidelines in RFC2623 when you mount an NFSv2 or v3 partition. (The same
> RFC also includes a brief discussion of the security implications of
> this model.)
>
> You'll need a patched version of "mount" though. The one distributed as
> part of Fedora Core 2 should work...
I looked through the FC2 util-linux patches and they seem to be mostly
identical to the CITI patches regarding the Kerberos support. And I've
already applied the CITI patches.
--
Pelle
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-08-30 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 18:41 NFSv3+Krb5 and mountd Per Olofsson
2004-08-30 1:41 ` Paul Jakma
2004-08-30 2:01 ` J. Bruce Fields
2004-08-30 15:45 ` Per Olofsson
2004-08-30 16:45 ` Trond Myklebust
2004-08-30 17:17 ` J. Bruce Fields
2004-08-30 17:45 ` Trond Myklebust
2004-08-30 18:04 ` J. Bruce Fields
2004-08-30 22:25 ` Trond Myklebust
2004-09-02 15:39 ` J. Bruce Fields
2004-08-30 21:54 ` Per Olofsson
2004-08-30 21:25 ` Per Olofsson [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=20040830212533.GN3671@nasse \
--to=pelle@dsv.su.se \
--cc=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=paul@clubi.ie \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.