From patchwork Wed Aug 14 16:37:42 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ard Biesheuvel X-Patchwork-Id: 171311 Delivered-To: patch@linaro.org Received: by 2002:a92:d204:0:0:0:0:0 with SMTP id y4csp1063513ily; Wed, 14 Aug 2019 09:37:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqwABIb7zDbg8Q/KEZvU/8CLCCjXO5jimxxkyE8z2Xw8i8sPlE76u461UWAzvjBvOzAkeO/X X-Received: by 2002:a17:90a:5884:: with SMTP id j4mr621127pji.142.1565800676559; Wed, 14 Aug 2019 09:37:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565800676; cv=none; d=google.com; s=arc-20160816; b=wdXVrIAHjeZ32XxfHXk5NAc+YcwOKRRYTxbonHQiXfFy/z6Nfmor2MN/1gIu7Fm9YO nyvH9FQPwMAAomH1EiF/0lA4I9eIeFU/Lo9HusNoDxwaM9RlPFzEzMXYeK4dp+RplYH/ iisDvMtzgHorpbn6Zm4bOruX7FvrgQfHzQTkPiSQbDe75HyjTT0B8UtvXt3Blh14r6wx c9Q66HvwKTJeRmDSjkrMXTweogBEQrZ8fZuaGQv4LD58LsOXQsctgI/zNMoaYqiXrudy d5KMJ1u8WaljxaSbtHb7e4BKgKEsAsf7TlHFeajt1Qr4NRjYWxrsKTYFCZvRqlsrcOVb MlFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature; bh=YrX5oOBk5fypgWbJscKxKeLPHT3qLuTnVQQLPTR0vac=; b=SykfEHCOyhv5OIPoxQfOGanRmGTLiL/V0nPO5yRUQW840BAg7NEp8UNT2m4YXbdwhZ 9/t4tJ/Ujk7flgQdGFpxYFEyh4B38KIm53N/2PlxOUXp/StwqXc9GBh0qjF54Kpf4/0Q k8xEzNowF9oc1FZZepTdtlpZJY2N2Hyx+2cQeI+TxWem6OevnaonKGGiQfYItwhcYtFR SoajPE47YL8sVQW3S4VLFMRkoJSV2d017xwTElMMcD2pt3NAXws0C1fqa3p/w5zmDxTL d+bLaX5Vxd6QaaJ0dclpPuc6krFCDNLKuWntt0LSQUwnuBxk4PAwTi2x2NqeoMZJUVal klLA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="HH43fx/4"; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t20si113594pgv.580.2019.08.14.09.37.56; Wed, 14 Aug 2019 09:37:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="HH43fx/4"; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726704AbfHNQhz (ORCPT + 3 others); Wed, 14 Aug 2019 12:37:55 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:47060 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726265AbfHNQhz (ORCPT ); Wed, 14 Aug 2019 12:37:55 -0400 Received: by mail-wr1-f68.google.com with SMTP id z1so111725132wru.13 for ; Wed, 14 Aug 2019 09:37:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=YrX5oOBk5fypgWbJscKxKeLPHT3qLuTnVQQLPTR0vac=; b=HH43fx/4WxeG034Z8g5xymkrpGH25FM4SFla/c6+uLtKbXJDeQ81MWvsUdQzkD0l6q O+5tcX875782QBTdD7F6rsy0/v+AdkjgwbKaLyqj+1HBWgnArvEbgkNzMr30iES6OjSJ olNSeGb2ThQRVljsx55UUVLSnUmwUwdEXdAsCCraNnaLxoyFg1vki+A6rq5xbiJgTfOE ErJ0SYP7zI7Xiu2JFeCGlne53BIFTQ5uy0JiRAc4GdstThv9fkEHF0JQfOJjdIJO4oPy ZbqoG9XKK0Bi7Mkb+SkeI2HHa8veJh2lyNYtteTuYnE4e/zVTh+nAkzBxp9qslIW1ct7 gjmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=YrX5oOBk5fypgWbJscKxKeLPHT3qLuTnVQQLPTR0vac=; b=hFB111zCNwnN7kcbIeJdOcIgH1lGZfPK8FkGOxxs6ZfUdjwcNqqzBM4BUwGx0C+21J hHIdRc/VJp1M4RqDm01QX4AO2RBRFPUmKd6KERjcLPFfb1vkeCT+3Q1Y/Qzvkh3tobcn jWQNSm5/wxtZrZD+HOMJHLZ7MJMVqyDc4fptTrmurRYMW+jvGCYTsETICJ19s4WmNxKs fuCwrasvqbXB1f6vcodUgEsf7/8b5DEnwARsnso+5XPbpRU0ITFg2uR4Q5PervOXdfp9 qYaBcqCR414MQa1NcE4kZqRvBVwuSkDn59Jl2IP3rwkmsR0Odw60OXs2IzU5eQxMM/4r NVZA== X-Gm-Message-State: APjAAAU8L2WUE1qKoNew37mHT2hyCUicMC2A17jX69Xt0C9FT/HyBdww sWnf/XA6tUHAtVeYKei/pDUJEwOgouxh9w== X-Received: by 2002:adf:db01:: with SMTP id s1mr694402wri.164.1565800671885; Wed, 14 Aug 2019 09:37:51 -0700 (PDT) Received: from localhost.localdomain ([2a02:587:a407:da00:1c0e:f938:89a1:8e17]) by smtp.gmail.com with ESMTPSA id 39sm610724wrc.45.2019.08.14.09.37.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Aug 2019 09:37:50 -0700 (PDT) From: Ard Biesheuvel To: linux-crypto@vger.kernel.org Cc: Ard Biesheuvel , Herbert Xu , Eric Biggers , dm-devel@redhat.com, linux-fscrypt@vger.kernel.org, Gilad Ben-Yossef , Milan Broz Subject: [PATCH v11 0/4] crypto: switch to crypto API for ESSIV generation Date: Wed, 14 Aug 2019 19:37:42 +0300 Message-Id: <20190814163746.3525-1-ard.biesheuvel@linaro.org> X-Mailer: git-send-email 2.17.1 Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org This series creates an ESSIV template that produces a skcipher or AEAD transform based on a tuple of the form ',' (or ',' for the AEAD case). It exposes the encapsulated sync or async skcipher/aead by passing through all operations, while using the cipher/shash pair to transform the input IV into an ESSIV output IV. Changes since v10: - Drop patches against fscrypt and dm-crypt - these will be routed via the respective maintainer trees during the next cycle - Fix error handling when parsing the cipher name from the skcipher cra_name - Use existing ivsize temporary instead of retrieving it again - Expose cra_name via module alias (#4) Changes since v9: - Fix cipher_api parsing bug that was introduced by dropping the cipher name parsing patch in v9 (#3). Thanks to Milan for finding it. - Fix a couple of instances where the old essiv(x,y,z) format was used in comments instead of the essiv(x,z) format we adopted in v9 Changes since v8: - Remove 'cipher' argument from essiv() template, and instead, parse the cra_name of the skcipher to obtain the cipher. This is slightly cleaner than what dm-crypt currently does, since we can get the cra_name from the spawn, and we don't have to actually allocate the TFM. Since this implies that dm-crypt does not need to provide the cipher, we can drop the parsing code from it entirely (assuming the eboiv patch I sent out recently is applied first) (patch #7) - Restrict the essiv() AEAD instantiation to AEADs whose cra_name starts with 'authenc(' - Rebase onto cryptodev/master - Drop dm-crypt to reorder/refactor cipher name parsing, since it was wrong and it is no longer needed. - Drop Milan's R-b since the code has changed - Fix bug in accelerated arm64 implementation. Changes since v7: - rebase onto cryptodev/master - drop change to ivsize in #2 - add Milan's R-b's Changes since v6: - make CRYPTO_ESSIV user selectable so we can opt out of selecting it even if FS_ENCRYPTION (which cannot be built as a module) is enabled - move a comment along with the code it referred to (#3), not that this change and removing some redundant braces makes the diff look totally different - add Milan's R-b to #3 and #4 Changes since v5: - drop redundant #includes and drop some unneeded braces (#2) - add test case for essiv(authenc(hmac(sha256),cbc(aes)),aes,sha256) - make ESSIV driver deal with assoc data that is described by more than two scatterlist entries - this only happens when the extended tests are being performed, so don't optimize for it - clarify that both fscrypt and dm-crypt only use ESSIV in special cases (#7) Changes since v4: - make the ESSIV template IV size equal the IV size of the encapsulated cipher - defining it as 8 bytes was needlessly restrictive, and also complicated the code for no reason - add a missing kfree() spotted by Smatch - add additional algo length name checks when constructing the essiv() cipher name - reinstate the 'essiv' IV generation implementation in dm-crypt, but make its generation function identical to plain64le (and drop the other methods) - fix a bug in the arm64 CE/NEON code - simplify the arm64 code by reusing more of the existing CBC implementation (patch #6 is new to this series and was added for this reason) Changes since v3: - address various review comments from Eric on patch #1 - use Kconfig's 'imply' instead of 'select' to permit CRYPTO_ESSIV to be enabled as a module or disabled entirely even if fscrypt is compiled in (#2) - fix an issue in the AEAD encrypt path caused by the IV being clobbered by the inner skcipher before the hmac was being calculated Changes since v2: - fixed a couple of bugs that snuck in after I'd done the bulk of my testing - some cosmetic tweaks to the ESSIV template skcipher setkey function to align it with the aead one - add a test case for essiv(cbc(aes),aes,sha256) - add an accelerated implementation for arm64 that combines the IV derivation and the actual en/decryption in a single asm routine Code can be found here https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=essiv-v11 Cc: Herbert Xu Cc: Eric Biggers Cc: dm-devel@redhat.com Cc: linux-fscrypt@vger.kernel.org Cc: Gilad Ben-Yossef Cc: Milan Broz Ard Biesheuvel (4): crypto: essiv - create wrapper template for ESSIV generation crypto: essiv - add tests for essiv in cbc(aes)+sha256 mode crypto: arm64/aes-cts-cbc - factor out CBC en/decryption of a walk crypto: arm64/aes - implement accelerated ESSIV/CBC mode arch/arm64/crypto/aes-glue.c | 206 ++++-- arch/arm64/crypto/aes-modes.S | 28 + crypto/Kconfig | 28 + crypto/Makefile | 1 + crypto/essiv.c | 667 ++++++++++++++++++++ crypto/tcrypt.c | 9 + crypto/testmgr.c | 14 + crypto/testmgr.h | 497 +++++++++++++++ 8 files changed, 1408 insertions(+), 42 deletions(-) create mode 100644 crypto/essiv.c -- 2.17.1