From: "J. Bruce Fields" <bfields@fieldses.org>
To: Raghu R <roverphoenix@gmail.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: NFS security
Date: Fri, 14 Oct 2005 11:56:54 -0400 [thread overview]
Message-ID: <20051014155654.GC26480@fieldses.org> (raw)
In-Reply-To: <f872993a0510140741l1ac0147ep1c6fea89b737434c@mail.gmail.com>
On Fri, Oct 14, 2005 at 07:41:26AM -0700, Raghu R wrote:
> I am sorry I mistyped that I had meant GSS-API and not GAA-API, I actually
> proposed to the professor today he says the scope of the project is huge for
> a single person for a perid of abt 2 months,
Probably so. And it's already been done, for the most part.
> the professor has suggested something simpler managable like a fix or
> something tp add to security to NFS, can you suggest some?
A couple rpcsec_gss loose ends that need doing:
* Fix mountd to enable auth_unix mount requests for krb5
mounts--needed by people doing rpcsec_gss over NFSv2/v3.
See http://bugzilla.linux-nfs.org/show_bug.cgi?id=57
* Add 3DES, AES, etc. support.
* Perform experiments to measure the rpcsec_gss performance
overhead.
And there are probably plenty of others depending on interest.
Make sure you let the list at nfsv4@linux-nfs.org know what you're
doing.
--b.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-10-14 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 7:04 NFS security Raghu R
2005-10-13 12:43 ` Trond Myklebust
2005-10-14 14:41 ` Raghu R
2005-10-14 15:52 ` Trond Myklebust
2005-10-14 15:56 ` J. Bruce Fields [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=20051014155654.GC26480@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=roverphoenix@gmail.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 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.