public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	Pierre Gondois <Pierre.Gondois@arm.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jian J Wang <jian.j.wang@intel.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH v2 1/1] SecurityPkg/RngDxe: Fix Rng algo selection for Arm
Date: Fri, 18 Nov 2022 10:10:24 +0000	[thread overview]
Message-ID: <ADF663FF-F7D4-43C8-B672-5538A48ABC40@arm.com> (raw)
In-Reply-To: <CAMj1kXEfxb8LUQApy=vDum6d8ETqBuitS8B3G3HgDVjtW0q+Zw@mail.gmail.com>

Hi Ard,

Please find my response inline marked [SAMI].

Regards,

Sami Mujawar

On 18/11/2022, 09:56, "Ard Biesheuvel" <ardb@kernel.org> wrote:

    On Wed, 16 Nov 2022 at 16:02, PierreGondois <pierre.gondois@arm.com> wrote:
    >
    > From: Pierre Gondois <pierre.gondois@arm.com>
    >
    > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4151
    >
    > The EFI_RNG_PROTOCOL can advertise multiple algorithms through
    > Guids. The PcdCpuRngSupportedAlgorithm contains a Guid that
    > can be configured. It represents the algorithm used in RngLib.
    > PcdCpuRngSupportedAlgorithm is set to the Zero Guid for KvmTool.
    >
    > When running KvmTool on a platform platform only having the RngLib,
    > the only Guid available for EFI_RNG_PROTOCOL will be the zero Guid.
    >
    > To select the default algorithm in EFI_RNG_PROTOCOL.GetRng():
    > a. Zero Guids are skipped
    > b. If no algorithm is found, an ASSERT is triggered
    >
    > To allow using the RngLib to be used for the case above, Zero Guids
    > should not be skipped (a.).
    > If no algorithm is found, don't prevent from booting on DEBUG builds
    > (b.).
    >
    > Allow Zero Guids to be selected and don't ASSERT if no algorithm is
    > found. Also simplify the selection of the Rng algorithm when the
    > default one is selected by just picking up the first element of
    > mAvailableAlgoArray.
    >
    > Reported-by: Sami Mujawar <sami.mujawar@arm.com>
    > Signed-off-by: Pierre Gondois <Pierre.Gondois@arm.com>

    I am still confused by this.

    Does this mean we might register the RNG protocol if we don't have
    anything to back it up?
[SAMI] From a Guest firmware implementation perspective, we do not know the available RNG source.
It may be CPU RNG, Arm FW TRNG or VIRTIO RNG. 
I would assume either one of CPU RNG or Arm FW TRNG would be implemented on the host platform. If none of these are present, we would want to fall back to VIRTIO RNG.

Considering this, I think we should not register the EFI_RNG_PRTOCOL if no supported algorithms are present.

The other argument would be that the protocol allows discovery of supported RNG source. But looking how this is consumed in Linux, I think it is better to not register EFI_RNG_PRTOCOL if no supported algorithms are present.

Please do let me know your thoughts.
[/SAMI]


    > ---
    >
    > Notes:
    >     v2:
    >     - Reformulate commit message.
    >     - Do not warn if no algorithm is found as the message
    >       would be printed on non-Arm platforms.
    >
    >  .../RandomNumberGenerator/RngDxe/ArmRngDxe.c      | 15 +++------------
    >  1 file changed, 3 insertions(+), 12 deletions(-)
    >
    > diff --git a/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c b/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c
    > index 5ba319899ce9..722d53386373 100644
    > --- a/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c
    > +++ b/SecurityPkg/RandomNumberGenerator/RngDxe/ArmRngDxe.c
    > @@ -76,7 +76,6 @@ RngGetRNG (
    >    )
    >  {
    >    EFI_STATUS  Status;
    > -  UINTN       Index;
    >
    >    if ((This == NULL) || (RNGValueLength == 0) || (RNGValue == NULL)) {
    >      return EFI_INVALID_PARAMETER;
    > @@ -86,21 +85,13 @@ RngGetRNG (
    >      //
    >      // Use the default RNG algorithm if RNGAlgorithm is NULL.
    >      //
    > -    for (Index = 0; Index < mAvailableAlgoArrayCount; Index++) {
    > -      if (!IsZeroGuid (&mAvailableAlgoArray[Index])) {
    > -        RNGAlgorithm = &mAvailableAlgoArray[Index];
    > -        goto FoundAlgo;
    > -      }
    > -    }
    > -
    > -    if (Index == mAvailableAlgoArrayCount) {
    > -      // No algorithm available.
    > -      ASSERT (Index != mAvailableAlgoArrayCount);
    > +    if (mAvailableAlgoArrayCount != 0) {
    > +      RNGAlgorithm = &mAvailableAlgoArray[0];
    > +    } else {
    >        return EFI_DEVICE_ERROR;
    >      }
    >    }
    >
    > -FoundAlgo:
    >    if (CompareGuid (RNGAlgorithm, PcdGetPtr (PcdCpuRngSupportedAlgorithm))) {
    >      Status = RngGetBytes (RNGValueLength, RNGValue);
    >      return Status;
    > --
    > 2.25.1
    >
    >
    >
    > ------------
    > Groups.io Links: You receive all messages sent to this group.
    > View/Reply Online (#96434): https://edk2.groups.io/g/devel/message/96434
    > Mute This Topic: https://groups.io/mt/95067856/5717338
    > Group Owner: devel+owner@edk2.groups.io
    > Unsubscribe: https://edk2.groups.io/g/devel/unsub [ardb+tianocore@kernel.org]
    > ------------
    >
    >


  reply	other threads:[~2022-11-18 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 15:01 [PATCH v2 1/1] SecurityPkg/RngDxe: Fix Rng algo selection for Arm PierreGondois
2022-11-18  9:55 ` [edk2-devel] " Ard Biesheuvel
2022-11-18 10:10   ` Sami Mujawar [this message]
2022-11-18 10:14     ` Ard Biesheuvel
2022-11-18 10:32       ` PierreGondois
2022-11-18 10:35         ` Ard Biesheuvel
2022-11-18 10:50           ` 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=ADF663FF-F7D4-43C8-B672-5538A48ABC40@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