RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

http://thread.gmane.org/gmane.comp.bios.edk2.devel/14498

Not committed to upstream yet, we should watch it.

Also, it probably makes sense to backport the CryptoPkg patches since our fork-off point, as we'll touch CryptoPkg for the sake of OpenSSL anyway:

  $ git log --oneline --reverse 988715a..master -- CryptoPkg/
  179bcd31f320 CryptoPkg: update openssl to ignore RVCT 3079
  ab6cee31e7dd CryptoPkg: Fix typos in comments
  8824c6144c73 CryptoPkg BaseCryptLib: Avoid passing NULL ptr to function
               BN_bn2bin()
  07cae0659795 CryptoPkg BaseCryptLib: Init the content of struct 'CertCtx'
               before

I'm adding the Security keyword just for good measure (+ marking the bug as security sensitive). The OpenSSL update is fully public in upstream (no CVE, embargo or anything).

I'd also like to use this BZ as a "test dummy" (i.e., make secalert aware that OVMF contains an embedded OpenSSL instance) while OVMF is Tech Preview.

Ultimately we should open up this bug to the public.

Affected SRPM version/release: ovmf-20160608-2.git988715a.el7

Testing: just sanity testing with key enrollment and secure boot feature testing (already part of QE's OVMF test plan).

Fix included in ovmf-20160608-3.git988715a.el7

Key enrollment and secure boot feature can work normally, so change its status to "Verified".

 Verified Version:
  Kernel Version:3.10.0-500.el7.x86_64
  qemu-kvm-version:qemu-kvm-rhev-2.6.0-22.el7.x86_64
  OVMF Version:OVMF-20160608-3.git988715a.el7.noarch

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2608.html