Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3DE38C433EF for ; Mon, 15 Nov 2021 14:18:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2538861B54 for ; Mon, 15 Nov 2021 14:18:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231805AbhKOOVh (ORCPT ); Mon, 15 Nov 2021 09:21:37 -0500 Received: from smtp-out2.suse.de ([195.135.220.29]:59094 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231669AbhKOOVa (ORCPT ); Mon, 15 Nov 2021 09:21:30 -0500 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id A3B2F1FD43; Mon, 15 Nov 2021 14:18:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1636985914; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=GC2dLbi5N9foZS2oN3h/VWN3NielyoujzJXaz6ERFuI=; b=DQesTKIx75nazpxfcsvtO27abuMTYyZEr6XcTOb/v4ZmwVC2hhpvGgXEjZtbF/+YOnfWHJ 9zh9WOM+LqUsygvUzQqfQG+mzvhZP6lE6DcylfdfQnsmFJGAIGdLY6PRby/ak+18f0yNrM /mAjtvsgHzqM7sjr/wAXs8eAaizAiew= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1636985914; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=GC2dLbi5N9foZS2oN3h/VWN3NielyoujzJXaz6ERFuI=; b=9GjhCqQwfAWYBU9sd+JLGwkfkebQ/QVl0zO7XPRUaH2KPH8dSEKJFvhA9G0LSqXrlhOtMu Dita8DBAwQActUDA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 849DD13476; Mon, 15 Nov 2021 14:18:34 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id qrkyHzpskmGGHwAAMHmgww (envelope-from ); Mon, 15 Nov 2021 14:18:34 +0000 From: Nicolai Stange To: =?UTF-8?q?Stephan=20M=C3=BCller?= , Herbert Xu , "David S. Miller" Cc: Torsten Duwe , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, Nicolai Stange Subject: [PATCH v2 0/6] crypto: DRBG - improve 'nopr' reseeding Date: Mon, 15 Nov 2021 15:18:03 +0100 Message-Id: <20211115141809.11420-1-nstange@suse.de> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi all, v1 can be found here: https://lore.kernel.org/r/20211025092525.12805-1-nstange@suse.de The changes between v1 and v2 are summarized below. Cover letter reproduced 1:1 from v1: This patchset aims at (hopefully) improving the DRBG code related to reseeding from get_random_bytes() a bit: - Replace the asynchronous random_ready_callback based DRBG reseeding logic with a synchronous solution leveraging rng_is_initialized(). This move simplifies the code IMO and, as a side-effect, would enable DRBG users to rely on wait_for_random_bytes() to sync properly with drbg_generate(), if desired. Implemented by patches 1-5/6. - Make the 'nopr' DRBGs to reseed themselves every 5min from get_random_bytes(). This achieves at least kind of a partial prediction resistance over the time domain at almost no extra cost. Implemented by patch 6/6, the preceding patches in this series are a prerequisite for this. Tested with and without fips_enabled in a x86_64 VM, both with random.trust_cpu=on and off. As confirmed with a couple of debugging printks() (added for testing only, not included in this series), DRBGs have been instantiated with and without rng_is_initialized() evaluating to true each during my tests and the patched DRBG reseeding code worked as intended in either case. Applies to current herbert/cryptodev-2.6.git master. Changes between v1 and v2: - 4/6: remove redundant goto statement, spotted by Stephan. For the unmodified rest, I added Stephan's Reviewed-bys he granted in reply to v1. Many thanks for your comments and remarks! Nicolai Nicolai Stange (6): crypto: DRBG - prepare for more fine-grained tracking of seeding state crypto: DRBG - track whether DRBG was seeded with !rng_is_initialized() crypto: DRBG - move dynamic ->reseed_threshold adjustments to __drbg_seed() crypto: DRBG - make reseeding from get_random_bytes() synchronous crypto: DRBG - make drbg_prepare_hrng() handle jent instantiation errors crypto: DRBG - reseed 'nopr' drbgs periodically from get_random_bytes() crypto/drbg.c | 143 +++++++++++++++++++++--------------------- include/crypto/drbg.h | 11 +++- 2 files changed, 80 insertions(+), 74 deletions(-) -- 2.26.2