Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1275147ybh; Thu, 16 Jul 2020 07:50:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwgJ8SqcDZV4TKIL6xsn+fumdFlKo/Bg4Smyjwr9w04FTfmpAMbdpTbN3nkFWv2dNDgfUm0 X-Received: by 2002:a17:906:1102:: with SMTP id h2mr3978524eja.356.1594911033285; Thu, 16 Jul 2020 07:50:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594911033; cv=none; d=google.com; s=arc-20160816; b=JIDUIobmM1eOlDZZmZIMAj+DPmmUGqQ6nP6jjEHx1cWgWcW41yPWwZz4ORYphUd4Vf h1FdLij88mK55WX5SHRS7cHC3yB3vajlyXLaf0Tcs/oJraYFpurdR1Qn62zospCnREWg 9LMtjIhdYm6HP4WyylYngcAUOZgaUOUex85m3+c4/+e+cLdVZOBKT1le2aL6XY9aRpsE Yu1Xgw/fc5/d/YgZ7I8t+/aFPXUsTfN3GYQD51K8AArMwjIhjNINbT1mHJJepmh/oFD5 hx2FHF2qHmYKnC4TqtvZj1FWeGaiHOjQnCKUoLQZMT2uEQZ2WR2gLj7D5ZjwhHFi7GA6 NJAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=OKPFCq7c4Tj37kL5lQQGIMWjl9wVJhrpQCoElsGxEbQ=; b=www+kj6v0UB1azHaYy0HghNrNboYGhW3aLEblXRoZ8yMx+nHUtV4xWhNCeVG9qLVRG dRmZade2c4L3T3aTNOP2OG7sZ7jHU+HoYV7tI30UrNOkarxH/gNZ42HcZ2ABVVLoBd+M jrxeUKWJH2T6nyL+iHQS7kvMcQrfTGXMC5SwZeynA6WK3i02XHWGWX+ykv/ipvTtNCa/ E5s2T0BHnYCOOd+rd7T6bk+aD8pRIcqGtMnpfH78IAOLwF2R5WdEQ/iGskyaV2FntJeG FJ18KRUCfV5mN5TSaVOTeFSt3DlRRhPoUB6gLnOsLKpAkU7iHHMJgz4ajepIeAc1ab2t YWTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@chronox.de header.s=strato-dkim-0002 header.b=mWlX4qGl; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z89si3344218ede.516.2020.07.16.07.50.06; Thu, 16 Jul 2020 07:50:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@chronox.de header.s=strato-dkim-0002 header.b=mWlX4qGl; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728541AbgGPOuD (ORCPT + 99 others); Thu, 16 Jul 2020 10:50:03 -0400 Received: from mo4-p00-ob.smtp.rzone.de ([85.215.255.24]:22132 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725867AbgGPOuD (ORCPT ); Thu, 16 Jul 2020 10:50:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1594910998; s=strato-dkim-0002; d=chronox.de; h=References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=OKPFCq7c4Tj37kL5lQQGIMWjl9wVJhrpQCoElsGxEbQ=; b=mWlX4qGlu8/qvtYxjJqSEVgFewp+xT1V2pNBCBozmoc/dGA0O0Oxuhv15w2n4qcfTz W/dUK5fM0iJcj5yTKDzvjwcaJk/00QBeg9UNz06mKAYmKtTMj8+JTbPsxD4wE6Mm/1tl GW9FZaz8fJ84Z6odERjUG0oX0gWEuyjJp/W0MRS2UllqvsHKAIUIATnNEot8e1UR0Idw u2HV+DWPx5N4HWVrplnQdLdv2fdfZ9RRH6dLZvloMu443w0DLQuKaYQ8FyQwA7oZLWmF /5B/YDPYLzCgF1o/aJVINpGFOnGP+dnJjF3EG5leceCdsdrAyX6CqsrFxrOQQgvfX9w7 rMgg== X-RZG-AUTH: ":P2ERcEykfu11Y98lp/T7+hdri+uKZK8TKWEqNyiHySGSa9k9x2wdNs6neUFoh7cs0E0=" X-RZG-CLASS-ID: mo00 Received: from tauon.chronox.de by smtp.strato.de (RZmta 46.10.5 AUTH) with ESMTPSA id y0546bw6GEnr95I (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Thu, 16 Jul 2020 16:49:53 +0200 (CEST) From: Stephan Mueller To: Elena Petrova Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Eric Biggers , Ard Biesheuvel , keyring@vger.kernel.org Subject: Re: [PATCH 0/1] crypto: af_alg - add extra parameters for DRBG interface Date: Thu, 16 Jul 2020 16:49:52 +0200 Message-ID: <5740551.2l3rmUXbR5@tauon.chronox.de> In-Reply-To: References: <20200713164857.1031117-1-lenaptr@google.com> <3312053.iIbC2pHGDl@tauon.chronox.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Am Donnerstag, 16. Juli 2020, 16:41:26 CEST schrieb Elena Petrova: Hi Herbert, > > > > With these issues, I would assume you are better off creating your own > > > > kernel module just like I did that externalizes the crypto API to user > > > > space but is only available on your test kernel and will not affect > > > > all > > > > other users. > > > > > > I considered publishing my kernel driver on GitHub, but there appears to > > > be > > > a sufficiently large number of users to justify having this > > > functionality > > > upstream. > > > > So, I should then dust off my AF_ALG KPP and AF_ALG akcipher patches then? > > :-D > Sure :) Long time ago when I released the patches now found in [1] and [2] they where rejected as it was said, the official route to access the RSA/ECDSA and the DH/ECDH ciphers is through the keyring. Obviously this interface of the keyring is not suitable for testing these algorithms. Considering the request that the kernel crypto API ciphers should be testable with arbitrary test vectors, would the dusted-off patches for AF_ALG KPP and akcipher be accepted? Ciao Stephan [1] https://github.com/smuellerDD/libkcapi/tree/master/kernel-patches/4.15-rc3/asym [2] https://github.com/smuellerDD/libkcapi/tree/master/kernel-patches/4.15-rc3/kpp