All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: jaganmohan kanakala <jaganmohan.kanakala@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: LINUX NFS support for SHA256 hash types
Date: Thu, 29 Sep 2022 16:18:52 +0000	[thread overview]
Message-ID: <2DC5A71F-F7B7-401B-954E-6A0656BDC6A9@oracle.com> (raw)
In-Reply-To: <CAK6vGwma1mALwE1zDUqXhGP+YHjtXdPipykui3Tt0a6NL_KOqw@mail.gmail.com>



> On Sep 28, 2022, at 8:04 AM, jaganmohan kanakala <jaganmohan.kanakala@gmail.com> wrote:
> 
> Hi Linux-NFS team,
> 
> I'm trying to set up the Kerberos5 setup with MIT as the KDC on my
> RHEL 8 machines.
> I'm able to get the setup working with Kerberos encryption types where
> the hash type is SHA1 (aes128-cts-hmac-sha1-96 and
> aes256-cts-hmac-sha1-96).
> 
> As SHA1 is kind of obsolete, my goal is to get my setup working for
> SHA256 hash types (aes128-cts-hmac-sha256-128,
> aes256-cts-hmac-sha384-192).
> 
> I tried that. The communication between the Linux client and MIT KDC
> is aes128-cts-hmac-sha256-128, but the communication between the Linux
> client and Linux NFS server is only aes256-cts-hmac-sha1-96.
> 
> When I checked the Linux upstream code I see that there is no support
> for SHA256 (and above) hash types.
> 
> https://github.com/torvalds/linux/blob/5bfc75d92efd494db37f5c4c173d3639d4772966/net/sunrpc/auth_gss/gss_krb5_mech.c
> 
> Have I looked at the right source code?
> Does the latest Linux NFS server has support for kerberos encryption
> types aes128-cts-hmac-sha256-128, aes256-cts-hmac-sha384-192 ?
> 
> Can anyone confirm?

As far as I know, the Linux in-kernel SunRPC RPCSEC GSS implementation
does not support the new encryption types defined in RFC 8009. That
means neither the in-kernel client or server support these types at
this time.

I'm not aware of plans to implement support for these. Cc'ing the
crypto mailing list to see if others are considering it.


--
Chuck Lever




  reply	other threads:[~2022-09-29 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 12:04 LINUX NFS support for SHA256 hash types jaganmohan kanakala
2022-09-29 16:18 ` Chuck Lever III [this message]
2022-10-07  9:27   ` jaganmohan kanakala
     [not found]   ` <CAK6vGw=50xecARE1MHmB73VrQS_OFzSqA5c1JF9AuOmjusUDNg@mail.gmail.com>
2024-03-25 14:33     ` [External] : " Chuck Lever III
2024-03-28 19:42       ` Scott Mayhew

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=2DC5A71F-F7B7-401B-954E-6A0656BDC6A9@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=dhowells@redhat.com \
    --cc=jaganmohan.kanakala@gmail.com \
    --cc=linux-crypto@vger.kernel.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 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.