public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"prarthanasv@ami.com" <prarthanasv@ami.com>,
	"POLUDOV, FELIX" <felixp@ami.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Sambandan, Vasudevan" <vasudevans@ami.com>,
	"Selvaraj, Sundaresan" <sundaresans@ami.com>,
	Gayathri Thunuguntla <gayathrit@ami.com>
Subject: Re: Coverity test for CryptoPkg
Date: Tue, 7 Jun 2022 23:12:26 +0000	[thread overview]
Message-ID: <CO1PR11MB492930891B5421944C335DD8D2A59@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BL0PR10MB3026F562A2AA9A4DB26D3D14B6DD9@BL0PR10MB3026.namprd10.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]

Hi Prarthana,

There are already some TianoCore BZs open on this topic.  Please see if the issues you want to fix are already noted and waiting for an owner.

https://bugzilla.tianocore.org/show_bug.cgi?id=1702

Also, Felix at AMI has a proposal to add Coverity for all EDK II packages.  I recommend you work with Felix to evaluate the issues.

https://edk2.groups.io/g/rfc/message/696

If you believe any of them are security issues, then please follow the following guidelines:

https://github.com/tianocore/tianocore.github.io/wiki/Reporting-Security-Issues

Thanks,

Mike

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Prarthana Sagar V via groups.io
Sent: Sunday, May 29, 2022 11:55 PM
To: devel@edk2.groups.io
Cc: Sambandan, Vasudevan <vasudevans@ami.com>; Selvaraj, Sundaresan <sundaresans@ami.com>; Gayathri Thunuguntla <gayathrit@ami.com>
Subject: [edk2-devel] Coverity test for CryptoPkg

Hello,

We would like to confirm whether any Coverity tests are performed for EDK2 CryptoPkg?
If no, please confirm if we can contribute the Coverity fix to edk2.

Thanks
Prarthana
-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.


[-- Attachment #2: Type: text/html, Size: 44146 bytes --]

      reply	other threads:[~2022-06-07 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  6:54 Coverity test for CryptoPkg Prarthana Sagar V
2022-06-07 23:12 ` Michael D Kinney [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=CO1PR11MB492930891B5421944C335DD8D2A59@CO1PR11MB4929.namprd11.prod.outlook.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