Received-SPF: pass (google.com: domain of linux-crypto+bounces-4109-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Fri, 10 May 2024 15:14:34 +0200
From: Marek =?UTF-8?B?QmVow7pu?= <kabel@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, Greg Kroah-Hartman
 <gregkh@linuxfoundation.org>
Subject: Is akcipher ready for userspace?
Message-ID: <20240510151434.739fd5c5@dellmb>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hello Herbert,

back in 2019 you wrote that akcipher is still in a state of flux and
not ready to be exposed to userspace via AF_ALG [1].

Has this changed since then?

I am asking because I am implementing another driver [2] for a device
which allows for signing messages with an ECDSA private key securely
stored inside the device, and Greg asks again [3] for this to be
exposed to userspace via a dedicated kernel API, instead of
debugfs.

Back in 2019 when we needed this for the turris-mox-rwtm driver, I
implemented it via debugfs because akcipher was not ready.

Thanks.

Marek

[1] https://www.spinics.net/lists/linux-crypto/msg38388.html
[2] https://lore.kernel.org/soc/20240510101819.13551-1-kabel@kernel.org/T/
[3] https://lore.kernel.org/soc/2024051042-unbuckled-barometer-1099@gregkh/