From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793867352; b=z43WFUMImTnp0YrRerqOEIFdZnHnBAYWbLxdTd2au/+ydBoVoln4DVQ07UHAjAtAIruy 1otJ5LtukKa3losnZ8LzHaazkwhcvDBbZEOAW+jK7yg6I4s1+IEt2QV8EdYKo3d/ziYMn uHdVrIBAkRPzR5FMRYSTzERuzZBJSTiQTEtwkNEL8NkIzBv24b847zZhRAtYonXZrrHmZ +kCqf5L8X59NyRYhGwUN9Oov7hEELxTR6k+sdOwSsnou7cbTO8PF3JRyl0psHPiAazR+r 8+CU15NfmJ+SpONcI5x/+zJGPRdi+TyL7hIFhVFF9S4vDt6v8j/a0T2Xr2whFCtMgIA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793867352; h=DMARC-Filter:DKIM-Signature:Received:X-MC-Unique: X-Mimecast-MFC-AGG-ID:Received:Received:From:To:Cc:Subject:Date: Message-ID:MIME-Version:Content-Transfer-Encoding:X-Scanned-By; bh=+rrAtFHqeMqdCjqPxg36A60/bzAo4VX4pdxWOCoyrs8=; b=4gWh3DjvQWitH9CtoW15/kg87RhDjxLwVQRRhDVfO9U1qmS4nmxm0S248/xNqAkY9oMJ 7tZ59hUyRsC8c9RBRGrND77ZwomiHyfSjP7BI2jGkvISotqQyrkdkQJ7S5SQgkujR2jvY WfkNp5rz8gaOEfUFV+dX9Iob9/bPyxatR0VQY/B1jNK6VxGT70qH9fmjVk4CYebeiAMYl LK9iOxnrnWTLIFRCHvgZRM3uApevsuZNCQD41YRpiiayut5VUmWVfLJlChF8rrZhPmLdf H4CtMJBd7goYXKY4W94kHAsUd0VkocRHG7Odzzuyi1fnprt6iw7YjKI+hlLhvuNtuDg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=hYg7KcEg; arc=none smtp.remote-ip=170.10.129.124 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2AD4A606A31B for ; Thu, 5 Nov 2026 08:29:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 2AD4A606A31B Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=hYg7KcEg DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1793867351; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=+rrAtFHqeMqdCjqPxg36A60/bzAo4VX4pdxWOCoyrs8=; b=hYg7KcEgvJJHynoXgSFFkdpA/69+zvLR4fT96UXUkwzb8Of7uzTCW0nP0EretHO6CVYW7z KVC3nqnK9yop6ThnWQcmP4rArm/gGyZ344Fijk4b/qcFGPN3DPVUgqtVjjaBfQ/GPsw6gC N0452L1UsrNq8ZAkQjQKO1n3+024eJs= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-355-dAP-xzHIOrWZ4hyhPfNwKw-1; Thu, 05 Nov 2026 03:29:08 -0500 X-MC-Unique: dAP-xzHIOrWZ4hyhPfNwKw-1 X-Mimecast-MFC-AGG-ID: dAP-xzHIOrWZ4hyhPfNwKw_1793867346 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 8674A19560B8; Thu, 5 Nov 2026 08:29:06 +0000 (UTC) Received: from thuth-p1g4.redhat.com (unknown [10.44.48.66]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 46F3D188458A; Thu, 5 Nov 2026 08:29:03 +0000 (UTC) From: Thomas Huth To: Eric Biggers Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, "Jason A. Donenfeld" , Ard Biesheuvel Subject: [PATCH v2] lib/crypto: Add a sentence about zeroizing raw key structures Date: Thu, 5 Nov 2026 09:29:02 +0100 Message-ID: <20261105082902.327526-1-thuth@redhat.com> X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 Let's make it clear that raw key material has to be zeroized, too. Suggested-by: Eric Biggers Signed-off-by: Thomas Huth --- v2: Move the information into a separate paragraph Documentation/crypto/libcrypto-zeroization.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/crypto/libcrypto-zeroization.rst b/Documentation/crypto/libcrypto-zeroization.rst index 76b6506711634..af3a4559b4963 100644 --- a/Documentation/crypto/libcrypto-zeroization.rst +++ b/Documentation/crypto/libcrypto-zeroization.rst @@ -43,6 +43,11 @@ two purposes: What to zeroize --------------- +Raw key material (e.g. a plain AES key stored in an array or a caller- +defined struct) must also be zeroized as soon as it is no longer needed, +for example right after it has been used to populate one of the key +structures below. + The following types of structures hold sensitive material and should be zeroized after use: -- 2.56.0