Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Quentin Godfroy <godfroy-7pss2ddYZfWsyDt4atOG6g@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: AES support for RPCSEC_GSS?
Date: Mon, 11 Feb 2008 23:37:15 -0500	[thread overview]
Message-ID: <20080212043715.GD4561@fieldses.org> (raw)
In-Reply-To: <20080212012007.GA6993-Gn1em/8t8udFYcqGaMRPHA@public.gmane.org>

On Tue, Feb 12, 2008 at 02:20:07AM +0100, Quentin Godfroy wrote:
> in all the faqs it is said that there is no working support for
> anything else than DES which is a bit outdated and not secure
> nowadays.
> 
> It seemed to me that there was some code in the nfs-utils which
> would do some security negociation (somewhere around utils/gssd/krb5_util.c),
> but the kernel had nothing to support that.
> 
> I suppose this will be the last thing to be done once the security features
> are working with the three versions of NFS.
> 
> What are the missing features in this field, and would it be difficult to
> add support for other encryption schemes?

Kevin Coffman is working on support for AES (and other algorithms).
It's mostly working at this point, so I think we'll be posting patches
soon.  Is there something in particular you need or want to work on?

--b.

  parent reply	other threads:[~2008-02-12  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  1:20 AES support for RPCSEC_GSS? Quentin Godfroy
     [not found] ` <20080212012007.GA6993-Gn1em/8t8udFYcqGaMRPHA@public.gmane.org>
2008-02-12  4:37   ` J. Bruce Fields [this message]
2008-02-13 17:01     ` Quentin Godfroy
     [not found]       ` <20080213170155.GA12551-Gn1em/8t8udFYcqGaMRPHA@public.gmane.org>
2008-02-13 17:59         ` J. Bruce Fields

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=20080212043715.GD4561@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=godfroy-7pss2ddYZfWsyDt4atOG6g@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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