All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	Jeff Barnes <jeffbarnes@microsoft.com>,
	Vladis Dronov <vdronov@redhat.com>,
	"marcelo.cerri@canonical.com" <marcelo.cerri@canonical.com>,
	Tyler Hicks <Tyler.Hicks@microsoft.com>,
	Shyam Saini <shyamsaini@microsoft.com>
Subject: [PATCH] crypto: JENT - set default OSR to 3
Date: Mon, 12 Aug 2024 08:25:42 +0200	[thread overview]
Message-ID: <2185508.xKdoZgZVDs@tauon.atsec.com> (raw)
In-Reply-To: <ZrRUzaPVqoDAcRLk@gondor.apana.org.au>

The user space Jitter RNG library uses the oversampling rate of 3 which
implies that each time stamp is credited with 1/3 bit of entropy. To
obtain 256 bits of entropy, 768 time stamps need to be sampled. The
increase in OSR is applied based on a report where the Jitter RNG is
used on a system exhibiting a challenging environment to collect
entropy.

This OSR default value is now applied to the Linux kernel version of
the Jitter RNG as well.

The increase in the OSR from 1 to 3 also implies that the Jitter RNG is
now slower by default.

Reported-by: Jeff Barnes <jeffbarnes@microsoft.com>
Signed-off-by: Stephan Mueller <smueller@chronox.com>
---
 crypto/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crypto/Kconfig b/crypto/Kconfig
index 72e2decb8c6a..a779cab668c2 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -1305,7 +1305,7 @@ config CRYPTO_JITTERENTROPY_MEMORY_BLOCKSIZE
 config CRYPTO_JITTERENTROPY_OSR
 	int "CPU Jitter RNG Oversampling Rate"
 	range 1 15
-	default 1
+	default 3
 	help
 	  The Jitter RNG allows the specification of an oversampling rate (OSR).
 	  The Jitter RNG operation requires a fixed amount of timing
-- 
2.46.0





  parent reply	other threads:[~2024-08-12  6:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM4PR21MB360932816FA7B848D7D8F7B0C7B82@DM4PR21MB3609.namprd21.prod.outlook.com>
2024-08-07 13:21 ` Intermittent EHEALTH Failure in FIPS Mode - jitterentropy jent_entropy_init() in Kernel 6.6.14 Stephan Mueller
2024-08-08  5:17   ` Herbert Xu
2024-08-08  5:56     ` Stephan Mueller
2024-08-08  6:10       ` Herbert Xu
2024-08-08  6:13         ` Stephan Mueller
2024-08-08  6:20           ` Herbert Xu
2024-08-08 14:08             ` [EXTERNAL] " Jeff Barnes
2024-08-12  6:25     ` Stephan Mueller [this message]
2024-08-24 13:48       ` [PATCH] crypto: JENT - set default OSR to 3 Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2185508.xKdoZgZVDs@tauon.atsec.com \
    --to=smueller@chronox.de \
    --cc=Tyler.Hicks@microsoft.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jeffbarnes@microsoft.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=marcelo.cerri@canonical.com \
    --cc=shyamsaini@microsoft.com \
    --cc=vdronov@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.