Linux NFS development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com, Scott Mayhew <smayhew@redhat.com>,
	Chuck Lever III <chuck.lever@oracle.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: Did the in-kernel Camellia or CMAC crypto implementation break?
Date: Thu, 13 Apr 2023 09:59:19 +0100	[thread overview]
Message-ID: <631678.1681376359@warthog.procyon.org.uk> (raw)
In-Reply-To: <ZDej9MCCCTAZEAsP@gondor.apana.org.au>

Herbert Xu <herbert@gondor.apana.org.au> wrote:

> So when did these last work for you?

Okay, this branch works:

	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rxgk

That's based on 5.10.0-rc4.  dmesg excerpt attached below.  This was before I
extracted the krb5 stuff out into its own lib.

On the other hand, I dug back through my crypto-krb5 branch to something based
on 5.16.0 and that doesn't work.

I can try forward porting my rxrpc-rxgk branch to try and find where it stops
working.

David
---
rxrpc: Running selftests
rxrpc: Running aes128-cts-hmac-sha256-128 prf
rxrpc: Running aes256-cts-hmac-sha384-192 prf
rxrpc: Running aes128-cts-hmac-sha256-128 key
rxrpc: Running aes256-cts-hmac-sha384-192 key
rxrpc: Running camellia128-cts-cmac key
alg: No test for cmac(camellia) (cmac(camellia-asm))
rxrpc: Running camellia256-cts-cmac key
rxrpc: Running aes128-cts-hmac-sha256-128 enc no plain
rxrpc: Running aes128-cts-hmac-sha256-128 enc plain<block
rxrpc: Running aes128-cts-hmac-sha256-128 enc plain==block
rxrpc: Running aes128-cts-hmac-sha256-128 enc plain>block
rxrpc: Running aes256-cts-hmac-sha384-192 enc no plain
rxrpc: Running aes256-cts-hmac-sha384-192 enc plain<block
rxrpc: Running aes256-cts-hmac-sha384-192 enc plain==block
rxrpc: Running aes256-cts-hmac-sha384-192 enc plain>block
rxrpc: Running camellia128-cts-cmac enc no plain
alg: No test for cts(cbc(camellia)) (cts(cbc-camellia-asm))
rxrpc: Running camellia128-cts-cmac enc 1 plain
rxrpc: Running camellia128-cts-cmac enc 1 plain
rxrpc: Running camellia128-cts-cmac enc 9 plain
rxrpc: Running camellia128-cts-cmac enc 13 plain
rxrpc: Running camellia128-cts-cmac enc 30 plain
rxrpc: Running camellia256-cts-cmac enc no plain
rxrpc: Running camellia256-cts-cmac enc 1 plain
rxrpc: Running camellia256-cts-cmac enc 9 plain
rxrpc: Running camellia256-cts-cmac enc 13 plain
rxrpc: Running camellia256-cts-cmac enc 30 plain
rxrpc: Running aes128-cts-hmac-sha256-128 mic
rxrpc: Running aes256-cts-hmac-sha384-192 mic
rxrpc: Running camellia128-cts-cmac mic abc
rxrpc: Running camellia128-cts-cmac mic ABC
rxrpc: Running camellia256-cts-cmac mic 123
rxrpc: Running camellia256-cts-cmac mic !@#
rxrpc: Selftests succeeded


  reply	other threads:[~2023-04-13  9:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 15:56 Did the in-kernel Camellia or CMAC crypto implementation break? David Howells
2023-04-12 16:57 ` Chuck Lever III
2023-04-12 17:44   ` Scott Mayhew
2023-04-12 17:50     ` David Howells
2023-04-13  6:07       ` Herbert Xu
2023-04-13  6:36         ` David Howells
2023-04-13  6:40           ` Herbert Xu
2023-04-13  8:59             ` David Howells [this message]
2023-04-13 13:55   ` David Howells
2023-04-14  2:08     ` Herbert Xu
2023-04-14  8:47       ` David Howells
2023-04-14  8:52         ` Herbert Xu
2023-04-14 10:17           ` David Howells
2023-04-14 10:18             ` Herbert Xu
2023-04-14 10:34               ` David Howells
2023-04-14 11:04                 ` Herbert Xu
2023-04-14 12:32               ` David Howells
2023-05-22 21:07           ` David Howells

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=631678.1681376359@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=ardb@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jlayton@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.com \
    /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