public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "PierreGondois" <pierre.gondois@arm.com>
To: devel@edk2.groups.io
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Zhiguang Liu <zhiguang.liu@intel.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jian J Wang <jian.j.wang@intel.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Jose Marinho <Jose.Marinho@arm.com>,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [edk2-devel] [PATCH v1 0/8] SecurityPkg/MdePkg: RngLib GUID
Date: Fri, 23 Jun 2023 11:01:33 +0200	[thread overview]
Message-ID: <7cff1caa-2f34-446f-8bf9-028efc361cdd@arm.com> (raw)
In-Reply-To: <175D69C984B78702.26836@groups.io>

Hello,
Just a ping for the patch-set,

Regards,
Pierre

On 5/9/23 09:40, PierreGondois via groups.io wrote:
> From: Pierre Gondois <pierre.gondois@arm.com>
> 
> This patchset follows the 'code first' approach and relies on [1].
> This patchset follows the thread at [3] that aims to solve [2].
> [1] and [2] are bound and this patchset aims to solve both.
> 
> In this patchset:
> a-
> The RngDxe can rely on the RngLib. However the RngLib has no
> interface allowing to describe which Rng algorithm is implemented.
> The RngDxe must advertise the algorithm that are available through
> the RngGetInfo() callback.
> Add a GetRngGuid() for interface to the RngLib.
> 
> b-
> The Arm Architecture states the RNDR that the DRBG algorithm should
> be compliant with NIST SP800-90A, while not mandating a particular
> algorithm, so as to be inclusive of different geographies.
> The RngLib can rely on this Arm RNDR instruction. In order to
> accurately describe the implementation using the RNDR instruction,
> add a EFI_RNG_ALGORITHM_ARM_RNDR GUID [1].
> 
> c-
> For the same reason as a/b, add a GUID describing unsafe RNG
> algorithms, allowing to accurately describe the BaseRngLibTimerLib.
> 
> d-
> Use a/b/c mechanisms/GUIDs to select a safe Rng algorithm in the
> Arm implementation of the RngDxe.
> 
> [1] BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4441
> [2] BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4151
> [3] https://edk2.groups.io/g/devel/message/100806
> 
> Pierre Gondois (8):
>    MdePkg/ArmTrngLib: Remove ASSERTs in Null implementation
>    MdePkg/MdePkg.dec: Move PcdCpuRngSupportedAlgorithm to MdePkg
>    MdePkg/DxeRngLib: Request raw algorithm instead of default
>    MdePkg/Rng: Add GUIDs to describe Rng algorithms
>    MdePkg/Rng: Add GetRngGuid() to RngLib
>    SecurityPkg/RngDxe: Use GetRngGuid() when probing RngLib
>    SecurityPkg/RngDxe: Select safe default Rng algorithm
>    SecurityPkg/RngDxe: Simplify Rng algorithm selection for Arm
> 
>   MdePkg/Include/Library/RngLib.h               | 17 +++++
>   MdePkg/Include/Protocol/Rng.h                 | 20 ++++++
>   .../BaseArmTrngLibNull/BaseArmTrngLibNull.c   |  4 --
>   MdePkg/Library/BaseRngLib/AArch64/Rndr.c      | 42 +++++++++++
>   MdePkg/Library/BaseRngLib/BaseRngLib.inf      |  9 +++
>   MdePkg/Library/BaseRngLib/Rand/RdRand.c       | 26 +++++++
>   .../Library/BaseRngLibNull/BaseRngLibNull.c   | 22 ++++++
>   .../BaseRngLibTimerLib/BaseRngLibTimerLib.inf |  3 +
>   .../Library/BaseRngLibTimerLib/RngLibTimer.c  | 28 ++++++++
>   MdePkg/Library/DxeRngLib/DxeRngLib.c          | 36 +++++++++-
>   MdePkg/MdePkg.dec                             |  7 ++
>   .../RngDxe/AArch64/AArch64Algo.c              | 70 +++++++++++++++----
>   .../RandomNumberGenerator/RngDxe/ArmRngDxe.c  | 23 +++---
>   .../RandomNumberGenerator/RngDxe/RngDxe.inf   |  5 +-
>   SecurityPkg/SecurityPkg.dec                   |  2 -
>   15 files changed, 278 insertions(+), 36 deletions(-)
> 

       reply	other threads:[~2023-06-23  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <175D69C984B78702.26836@groups.io>
2023-06-23  9:01 ` PierreGondois [this message]
2023-06-25  3:13   ` 回复: [edk2-devel] [PATCH v1 0/8] SecurityPkg/MdePkg: RngLib GUID gaoliming
2023-06-27  7:19     ` PierreGondois

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=7cff1caa-2f34-446f-8bf9-028efc361cdd@arm.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