public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Thomas Abraham <thomas.abraham@arm.com>, devel@edk2.groups.io
Cc: Sami Mujawar <sami.mujawar@arm.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Matteo.Carlini@arm.com, Ben.Adderson@arm.com, nd@arm.com
Subject: Re: [edk2-devel] [PATCH edk2-platforms v1 1/1] Platform/ARM: TimerLib based RngLib for CryptoPkg
Date: Sun, 4 Oct 2020 18:44:20 +0200	[thread overview]
Message-ID: <1c03406f-09aa-4343-0886-76375568d726@arm.com> (raw)
In-Reply-To: <CAJuA9ahZMyhm0yiyaq6VOMHY0xQRfWhWhHjE7TTq=Oo+oA-vvg@mail.gmail.com>

On 10/2/20 4:12 PM, Thomas Abraham wrote:
> On Fri, Oct 2, 2020 at 1:49 PM Ard Biesheuvel <ard.biesheuvel@arm.com> wrote:
>>
>> On 10/2/20 1:15 AM, Sami Mujawar wrote:
>>> The commit at "b5701a4c7a0f CryptoPkg: OpensslLib: Use RngLib to
>>> generate entropy in rand_pool" updated CryptoPkg\OpenSSL to no
>>> longer depend on TimerLib and instead use RngLib. This is done so
>>> that platforms can choose the desired entropy source. However, this
>>> change breaks the builds for platforms under Platform/ARM.
>>>
>>> To fix this, update ArmVExpress.dsc.inc to use a TimerLib based
>>> implementation of RngLib.
>>>
>>> Note: The TimerLib based implementation of RngLib replicates past
>>> behavior when used with OpenSSL. However, this should not be used
>>> in production as a real source of entropy.
>>>
>>> Signed-off-by: Sami Mujawar <sami.mujawar@arm.com>
>>
>> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> 
> Tested for SGI/RD platforms and it resolves the build issue.
> 
> Tested-by: Thomas Abraham <thomas.abraham@arm.com>
> 

Pushed as 96a98e4d3255..fc49849a8ebc

Thanks,

      reply	other threads:[~2020-10-04 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 23:15 [PATCH edk2-platforms v1 1/1] Platform/ARM: TimerLib based RngLib for CryptoPkg Sami Mujawar
2020-10-02  8:19 ` Ard Biesheuvel
2020-10-02 14:12   ` [edk2-devel] " Thomas Abraham
2020-10-04 16:44     ` Ard Biesheuvel [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-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=1c03406f-09aa-4343-0886-76375568d726@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