public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel via groups.io" <ardb=kernel.org@groups.io>
To: Pierre.Gondois@arm.com
Cc: devel@edk2.groups.io, sami.mujawar@arm.com,
	 Thomas Abraham <thomas.abraham@arm.com>
Subject: Re: [edk2-devel] [PATCH 0/3] Platform/ARM/Juno: Use RngDxeLib
Date: Wed, 4 Sep 2024 14:05:13 +0200	[thread overview]
Message-ID: <CAMj1kXEh4xu9+EZZT7asPe3MnP7d7B0=qdMb9Wqdgo0N-Yvx4Q@mail.gmail.com> (raw)
In-Reply-To: <20240904113905.1736428-1-Pierre.Gondois@arm.com>

On Wed, 4 Sept 2024 at 13:39, <Pierre.Gondois@arm.com> wrote:
>
> From: Pierre Gondois <pierre.gondois@arm.com>
>
> Juno's RngLib implementation is:
>
> - BaseRngLib.inf if a secure RngLib is enforced
> - BaseRngLibTimerLib.inf if a non-secure RngLib is tolerated
>
> BaseRngLib.inf relies on the Arm's RNDR instruction. The instruction
> returns a DRBG-generated random number. The DRBG used is considered
> as secure.
> The RNDR instruction is available if FEAT_RNG is set. The Juno doesn't
> support it.
>
> When security is enforced (i.e. ENABLE_UNSAFE_RNGLIB is not set),
> the Juno cannot generate secure random numbers through the RngLib.
> Secure random numbers could be generated by using the Juno's TRNG.
> This can be done by:
>
> - using the RngDxeLib implementation of the RngLib
> - RngDxeLib relies on the RngDxe
> - the RngDxe has access to the TRNG
>
> Pierre Gondois (3):
>   Platform/ARM: Place MdeLibs.dsc.inc as the first include
>   Platform/ARM: Move PcdEnforceSecureRngAlgorithms to MdePkg
>   Platform/ARM/Juno: Use DxeRngLib.inf as default RngLib implementation
>

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>

Please ping me when this can be merged.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120494): https://edk2.groups.io/g/devel/message/120494
Mute This Topic: https://groups.io/mt/108262991/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2024-09-04 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 11:39 [edk2-devel] [PATCH 0/3] Platform/ARM/Juno: Use RngDxeLib PierreGondois
2024-09-04 11:39 ` [edk2-devel] [PATCH 1/3] Platform/ARM: Place MdeLibs.dsc.inc as the first include PierreGondois
2024-09-04 11:39 ` [edk2-devel] [PATCH 2/3] Platform/ARM: Move PcdEnforceSecureRngAlgorithms to MdePkg PierreGondois
2024-09-04 11:39 ` [edk2-devel] [PATCH 3/3] Platform/ARM/Juno: Use DxeRngLib.inf as default RngLib implementation PierreGondois
2024-09-04 12:05 ` Ard Biesheuvel via groups.io [this message]
2024-09-04 12:31 ` [edk2-devel] [PATCH 0/3] Platform/ARM/Juno: Use RngDxeLib Sami Mujawar

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-list 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='CAMj1kXEh4xu9+EZZT7asPe3MnP7d7B0=qdMb9Wqdgo0N-Yvx4Q@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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