[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1478993.1736493228@warthog.procyon.org.uk>
Date: Fri, 10 Jan 2025 07:13:48 +0000
From: David Howells <dhowells@...hat.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: dhowells@...hat.com, Herbert Xu <herbert@...dor.apana.org.au>,
Chuck Lever <chuck.lever@...cle.com>,
Trond Myklebust <trond.myklebust@...merspace.com>,
"David S. Miller" <davem@...emloft.net>,
Marc Dionne <marc.dionne@...istor.com>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
linux-crypto@...r.kernel.org, linux-afs@...ts.infradead.org,
linux-nfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 2/8] crypto/krb5: Provide Kerberos 5 crypto through AEAD API
Eric Biggers <ebiggers@...nel.org> wrote:
> It sounds like a lot of workarounds had to be implemented to fit these
> protocols into the crypto_aead API.
>
> It also seems unlikely that there will be other implementations of these
> protocols added to the kernel, besides the one you're adding in crypto/krb5/.
>
> Given that, providing this functionality as library functions instead would be
> much simpler. Take a look at how crypto/kdf_sp800108.c works, for example.
Yes. That's how I did my first implementation. I basically took the code
from net/sunrpc/auth_gss/ and made it more generic. Herbert wants it done
this way, however. :-/
David
Powered by blists - more mailing lists