From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by mx.groups.io with SMTP id smtpd.web08.7326.1613480994607317311 for ; Tue, 16 Feb 2021 05:09:54 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: linux.intel.com, ip: 134.134.136.31, mailfrom: maciej.rabeda@linux.intel.com) IronPort-SDR: LpPrCohvNRHUZ4yYs5CqtyGMhilbrqQoSgw6xzgqiH32LLFdZOSqO/LUtWjLuqrMkYpcwD0VDJ qXOnm0OjehEQ== X-IronPort-AV: E=McAfee;i="6000,8403,9896"; a="244356394" X-IronPort-AV: E=Sophos;i="5.81,183,1610438400"; d="scan'208,217";a="244356394" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Feb 2021 05:09:53 -0800 IronPort-SDR: Q4Mm73s+CvRUOV+mT1PL3O96thVs+UIy7vIT5l8+4tPR+sfR6PCjajvoVpsR6GqTY3JhG30Vq/ H2PGrBGRP8sQ== X-IronPort-AV: E=Sophos;i="5.81,183,1610438400"; d="scan'208,217";a="384382085" Received: from mrabeda-mobl.ger.corp.intel.com (HELO [10.249.143.157]) ([10.249.143.157]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Feb 2021 05:09:52 -0800 Subject: Re: [edk2-devel] reg: RNG functions Usage in NetworkPkg To: devel@edk2.groups.io, sivaramann@amiindia.co.in Cc: Lavanya Paneerselvam References: <1660715EBDF480CD.8308@groups.io> From: "Maciej Rabeda" Message-ID: <9c0d93b4-27b2-7991-a3f3-fcc157f90098@linux.intel.com> Date: Tue, 16 Feb 2021 14:09:44 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------72A6214F17E8F29566EDDB21" Content-Language: pl --------------72A6214F17E8F29566EDDB21 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Hi Siva, I am not proactively trying to change that. NET_RANDOM is used throughout the network stack and touching it would require solid regression. Is there any defect requiring such a change? Thanks, Maciej On 12-Feb-21 06:52, Sivaraman Nainar wrote: > > Hello Maciej: > > Do you have any comment on this. > > -Siva > > *From:* devel@edk2.groups.io [mailto:devel@edk2.groups.io] *On Behalf > Of *Sivaraman Nainar > *Sent:* Thursday, February 4, 2021 10:05 AM > *To:* Rabeda, Maciej; devel@edk2.groups.io > *Cc:* Lavanya Paneerselvam > *Subject:* [edk2-devel] reg: RNG functions Usage in NetworkPkg > > Hello Maciej: > > Do we have any plan to use the RNG Library function in the Macro > “*NET_RANDOM” *of NetworkPkg. > > ** > > NET_RANDOM can use *GetRandomNumber32() *which is more reliable right? > > ** > > Thanks > > Siva > > This e-mail is intended for the use of the addressee only and may > contain privileged, confidential, or proprietary information that is > exempt from disclosure under law. If you have received this message in > error, please inform us promptly by reply e-mail, then delete the > e-mail and destroy any printed copy. Thank you. > > --------------72A6214F17E8F29566EDDB21 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit Hi Siva,

I am not proactively trying to change that.
NET_RANDOM is used throughout the network stack and touching it would require solid regression.
Is there any defect requiring such a change?

Thanks,
Maciej

On 12-Feb-21 06:52, Sivaraman Nainar wrote:

Hello Maciej:

Do you have any comment on this.

-Siva

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Sivaraman Nainar
Sent: Thursday, February 4, 2021 10:05 AM
To: Rabeda, Maciej; devel@edk2.groups.io
Cc: Lavanya Paneerselvam
Subject: [edk2-devel] reg: RNG functions Usage in NetworkPkg

Hello Maciej:

Do we have any plan to use the RNG Library function in the Macro “NET_RANDOM” of NetworkPkg.

NET_RANDOM can use GetRandomNumber32() which is more reliable right?

Thanks

Siva

This e-mail is intended for the use of the addressee only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.

--------------72A6214F17E8F29566EDDB21--