public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Luse, Paul E" <paul.e.luse@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Status of OpenSSL 3.0 patch
Date: Wed, 17 May 2023 20:55:24 +0000	[thread overview]
Message-ID: <CO1PR11MB4836F5AEB2BB7A9F7DCFC96BAD7E9@CO1PR11MB4836.namprd11.prod.outlook.com> (raw)

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

Hello Tianocore Community!

I’m a software developer working on a storage product that uses just a few EDK II / OpenSSL functions related to key derivation in support of self-encrypting drives.  We were recently made aware of the pending EOL of the current OpenSSL in EDK II and have a release of our product coming up soon so are trying to get some insight into the following patch https://github.com/tianocore/edk2-staging/tree/OpenSSL11_EOL.

Both myself and several of my team members have a decent amount of open source experience but not with Tianocore and nothing with OpenSSL either.   So mostly what I’m looking for is some information on:


  *   Status/next steps on the patch above.  Who is driving, do they have a specific date range/goal for landing?
  *   Is anyone else out there a consumer of this and also in need of timely resolution, maybe we can brainstorm some thoughts?

I would *love* to be able to jump in and help with the patch but with our lack of experience here, I’m afraid we might just slow things down.  But, I’m open to any and all suggestions :)

Thanks!
Paul

PS: FYI I’ll be attending the next community meeting as well so look forward to talking some more about it there as well.




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

                 reply	other threads:[~2023-05-17 20:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CO1PR11MB4836F5AEB2BB7A9F7DCFC96BAD7E9@CO1PR11MB4836.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