From: Shivam Kumar <shivam.kumar1@nutanix.com>
To: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: herbert@gondor.apana.org.au, aquini@redhat.com,
jeremy.wayne.powell@gmail.com, clemens@ladisch.de,
pwalten@au1.ibm.com, joe@perches.com
Subject: Question: Earliest kernel version with FIPS-compliant DRBG?
Date: Tue, 7 Nov 2023 11:04:42 +0530 [thread overview]
Message-ID: <5cc50864-9096-497b-a86f-e37678dcb105@nutanix.com> (raw)
Hi,
I recently came across a discussion on the mailing list and noted some
Linux Kernel Mailing List (LKML) patches pertaining to the enhancement
of the kernel's Deterministic Random Bit Generator (DRBG) to meet FIPS
(Federal Information Processing Standards) compliance. However, I am
currently uncertain about the status of this endeavor, specifically
whether the kernel's DRBG has indeed been rendered FIPS-compliant.
Could you kindly provide clarification on the current status of the
kernel's DRBG in this regard? Furthermore, if it has been made
FIPS-compliant, I am keen to ascertain the earliest kernel version that
incorporates this FIPS-compliant DRBG.
Thanks,
Shivam
reply other threads:[~2023-11-07 5:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5cc50864-9096-497b-a86f-e37678dcb105@nutanix.com \
--to=shivam.kumar1@nutanix.com \
--cc=aquini@redhat.com \
--cc=clemens@ladisch.de \
--cc=herbert@gondor.apana.org.au \
--cc=jeremy.wayne.powell@gmail.com \
--cc=joe@perches.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pwalten@au1.ibm.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 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®