[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <493307.1737102616@warthog.procyon.org.uk>
Date: Fri, 17 Jan 2025 08:30:16 +0000
From: David Howells <dhowells@...hat.com>
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
David Howells <dhowells@...hat.com> wrote:
> > rfc8009 is basically the same as authenc.
>
> Actually, it's not quite the same :-/
>
> rfc8009 chucks the IV from the encryption into the hash first, but authenc()
> does not. It may be possible to arrange the buffer so that the assoc data is
> also the IV buffer.
Actually actually, it's the starting IV, so I just need to chuck in a block of
zeroes.
David
Powered by blists - more mailing lists