From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795048653; b=5rp2IqiE0GkFU6GYwEraqJ0tzr7/qr/A5ifbPZPvoXUOLNOEPNRVTaABtGuhljs0P1fv 5KhgLAo5nGtIDdcxIaMUKrRh9wILPPwTjKadZwP9HFlalWNA0OBrcxkfn8qZunbRMUqgM dOYr+eHW3PxFP9uZ6d1SVeunWpLPKnENqQnJHVkCf6/eYDJCyJCDu1MQhPS2gC5VIrYf9 bpyyIhbsSEtzDefic/dagvbExSJc1xJ6yfiecpA3Pwm75jXPoMleFDqy9cUIPYILzGhtn +1mIopuY1MdL9Jc/WxQPiv1XJoDao1Ctp9ZURC9rCMOd8So3wNKkEx/oaKkP8zHDM6Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795048653; h=Received:DKIM-Signature:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; bh=oAmABwcXXotQ3MKjKlI/9ynn2ibq7W7A2AvNHWEPewY=; b=GKUR3ZPOw+EwtFfAtIqiBG0cs+jeKeTiJRql1BykLx2a5R2tacRQUUI9QjlIqQBuOqlB QrYBBDth35u3EUJ305eV/CLGsnT0RB2JhckKmlb1Mzf3PbMyxIt6JPHPj31RPMtSmd97+ y2s+qeVziG1YR3fxEsFPj4yTzpgcuve5nPlFIW1bkW48Po3/O+zE8c4cpjSwHgBSxPW7i 893DImoW/hSSni17/I34GQUXbXRjJ73Em25MSITK9M+rmQMC7XaHaoMlkTx7Sn09bQcxx /RUpiUvzRiupeiBTRkLYXGn7Ycxqk5UkXzG1XBLhFaXE0RWtPZlkJagDz3EolyraMSw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=h+plfSKN; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with UTF8SMTPS id A0EF4606A330; Thu, 19 Nov 2026 00:37:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=h+plfSKN Received: by smtp.kernel.org (Postfix) with UTF8SMTPSA id DBFE31F000C7; Thu, 19 Nov 2026 00:37:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1795048653; bh=oAmABwcXXotQ3MKjKlI/9ynn2ibq7W7A2AvNHWEPewY=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=h+plfSKN+NLklqzjVemtZ32v59otj6WZ+i5ZX7AJNaHRwkty60vwf5CANYwQxXadx 9grKaSXHcL88gyAjvmXj7Dxj3igtLg6VRA9BkS2Xz+sbkPiCJQ65NyUYXBfOPbFLaf XdoVCRs1sK9pCYlYYliMAoWSNOquomqnVLl3/oQYKhVOXjNB/2YkLR+ZmUSK7vARM2 NrnppZL015i7TMfc06dS3AIYzWHi0I0F9oDGYTm5PYv5MbnqgOyCcmXq05dDZE4G/8 9EcXCPKRRhyeREJcSq+0h5D+bY7R62ppVpH/JRlvhOiY5Ob80r79UOhLIEBJXASLY8 Zf17RFO2AFGOw== Date: Thu, 19 Nov 2026 02:37:29 +0200 From: Jarkko Sakkinen To: Demi Marie Obenour Cc: Rodolfo Giometti , David Howells , keyrings@vger.kernel.org, Herbert Xu , "David S. Miller" , Jens Wiklander , Sumit Garg , op-tee@lists.trustedfirmware.org, Horia =?utf-8?Q?Geant=C4=83?= , Pankaj Gupta , Sahil Malhotra , Ahmad Fatoum , Richard Weinberger , "Christophe Leroy (CS GROUP)" , Eric Biggers , Arnd Bergmann , Paul Moore , James Morris , "Serge E. Hallyn" , Jonathan Corbet , Shuah Khan , Randy Dunlap , linux-crypto@vger.kernel.org, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org, linux-api@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 0/9] KEYS: keycrypt: keys that user space can use but never read Message-ID: References: <20261118140421.584086-1-giometti@enneenne.com> <650f89ef-9745-4f75-b254-80fa5ac4773d@gmail.com> X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <650f89ef-9745-4f75-b254-80fa5ac4773d@gmail.com> On Wed, Nov 18, 2026 at 06:42:15PM -0500, Demi Marie Obenour wrote: > On 11/18/26 9:04 AM, Rodolfo Giometti wrote: > > This RFC proposes a key type, "keycrypt", whose material user space can > > use for symmetric operations but never read: AES-256-CBC, HMAC-SHA256 > > and an authenticated AES-256-GCM stream, through a file descriptor that > > KEYCTL_CRYPT_OPEN returns for one key and one operation. > > I haven't looked at the API, but from a cryptographic perspective, > this encourages very poor practices. AES-GCM even allows userspace > to extract the secret authentication key. > > AES-256-CBC isn't a suitable mode on its own, unless it's combined > with a MAC in encrypt-then-MAC. Even then, it has a 2^64 birthday > bound, so it should only be used 2^48 times with a single key unless > the key is ephemeral. > > AES-GCM is not a suitable algorithm either. If you allow encrypting > with a key loaded from persistent storage, there is no way for the API > to ensure it is only used with a unique nonce. Nonce reuse leaks the > authentication key and allows forgeries. Using random nonces isn't > good enough either: NIST only allows 2^32 encryptions in this case, > and the API can't enforce that limit. > > For long-term keys, all of the following are much safer choices. > They have 192-bit nonces, which means that one can generate them > at random for each encryption without any problems. > > - XAES-256-GCM > - XChaCha20-Poly1305 > - AEGIS-256 > > AES-GCM-SIV is also okay, provided that you are fine with occasionally > leaking if two plaintexts are equal. This happens whenever there is > a nonce collision, so with probability 2^-32 after 2^32 encryptions. The exitential problem here is that KEYCTL_CRYPT_OPEN creates a circular relationship between the keyrings API and a specific key type. At hardware level I did not see any support for TPM, which narrows down the potential user base. The remaining potential user base is further reduced by those that use trusted keys; leaving out those who need to solve the assumed problem that only this patch set can presumebly sort out. And we don't really know at this point that cut. This is pretty much the break down of what is wrong here. If there is/was a problem to sort out, it should be so constrained that it should be as quick to describe as stepping over a nail really. These are the main topics what I would focus on. > -- > Sincerely, > Demi Marie Obenour (she/her/hers) Br, Jarkko