From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto <linux-crypto@vger.kernel.org>
Cc: Robert Elliott <elliott@hpe.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Christoph Biedl <bugzilla.kernel.bpeb@manchmal.in-ulm.de>
Subject: Re: CONFIG_JITTERENTROPY needs more explanation?
Date: Sun, 18 Feb 2024 12:32:05 +0700 [thread overview]
Message-ID: <ZdGWVVIZx8uIu83K@archie.me> (raw)
In-Reply-To: <8992c7f0-b0b1-4bbb-b5a3-2906159e2e24@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Sat, Feb 17, 2024 at 08:56:48AM -0800, Randy Dunlap wrote:
>
>
> On 2/6/24 06:26, Bagas Sanjaya wrote:
> > Hi,
> >
> > On Bugzilla, Christoph Biedl <bugzilla.kernel.bpeb@manchmal.in-ulm.de>
> > wrote a question on CRYPTO_JITTERENTROPY description [1]:
> >
> >> The desciption of the CRYPTO_JITTERENTROPY kernel option in crypto/Kconfig has an incomplete sentence:
> >>
> >> | This RNG does not perform any cryptographic whitening of the generated
> >> |
> >> | See https://www.chronox.de/jent.html
> >>
> >> This was introduced in a9a98d49da52 ("crypto: Kconfig - simplify compression/RNG entries") - please fix when convenient.
> >
> > Can you explain why the Kconfig description says so?
> >
> > Thanks.
> >
> > [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218458
> >
>
> Hi,
> Fixup patch has been posted.
> Thanks for the report.
>
> Subject: should be CRYPTO_JITTERENTRY.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-02-18 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:26 Bagas Sanjaya
2024-02-17 16:56 ` Randy Dunlap
2024-02-18 5:32 ` Bagas Sanjaya [this message]
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=ZdGWVVIZx8uIu83K@archie.me \
--to=bagasdotme@gmail.com \
--cc=bugzilla.kernel.bpeb@manchmal.in-ulm.de \
--cc=davem@davemloft.net \
--cc=elliott@hpe.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®