Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-33741

Please stop using OpenSSL ENGINE API in mstflint

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhel-10.0.beta
    • rhel-10.0
    • mstflint
    • None
    • mstflint-4.26.0-5.el10
    • None
    • Important
    • 3
    • rhel-sst-network-drivers
    • ssg_networking
    • 16
    • 18
    • 5
    • Dev ack
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • Network Driver 2, Network Driver 4, Network Driver 3
    • All
    • None

      Dear colleagues,

      Our scanning identified your component as one of the packages using OpenSSL ENGINE API.

      Engines are not FIPS compatible and corresponding API is deprecated since OpenSSL 3.0. The engine functionality we are aware of (PKCS#11, TPM) is either covered by providers maintained by Crypto Team now or will be covered soon.

      We kindly ask you to implement patches or apply compiling options to eliminate the code relying on ENGINE API. Even if we don’t eliminate the ENGINE API completely for backward binary compatibility, the compilation of applications using the ENGINE API will soon become impossible.

      We kindly ask you to add this work to the nearest sprint. We have a side-tag f41-build-side-86419 to build and a Copr build https://copr.fedorainfracloud.org/coprs/dbelyavs/openssl-no-engine/build/7107098/

      Feel free to reach the Crypto team, Dmitry Belyavskiy, Sahana Prasad, or Clemens Lang directly if you have any problems with the necessary changes.

              kheib Kamal Heib
              autobot-jira-api pme bot
              Kamal Heib Kamal Heib
              Afom Michael Afom Michael
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: