Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-1011

Bridge BoringSSL API to OpenSSL

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Envoy, Maistra
    • None
    • Bridge BoringSSL API to OpenSSL
    • False
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done

      Develop a bridge layer that implements BoringSSL using OpenSSL.  The goal is to contain the effort required to maintain a version of Envoy that uses OpenSSL to a distinct code base/project.  Currently, all code that access BoringSSL is replaced with OpenSSL calls, which frequently creates merge conflicts as the Envoy project evolves.  In addition to Envoy itself, some additional libraries used by Envoy have started to have dependencies on BoringSSL as well.

      • Add a list of BoringSSL calls made by upstream envoy i.e. the calls we need to support in our layer
      • Implement the required API calls, and reuse the corresponding BoringSSL utests here possible
      • Work out how to incrementally integrate the layer into maistra/envoy, if possible, to verify progress.
      • support for x64 and IBM platforms

      Related

              rhn-support-twalsh Tim Walsh
              rcernich1 Rob Cernich
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: