Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-24435

[2161719] After HCO crypto policy set to 'Old', connection doesn't use TLSv1.1

XMLWordPrintable

    • Moderate
    • None

      Description of problem:
      -----------------------
      When HCO is set with crypto policy profile 'Old' or 'Custom' profile with minTLSVersion as 'VersionTLS11', the connection doesn't uses as TLSv1.1

      Version-Release number of selected component (if applicable):
      -------------------------------------------------------------
      CNV v4.12.0

      How reproducible:
      -----------------
      Always

      Steps to Reproduce:
      -------------------
      1. Set HCO crypto profile as Old (hco.spec.tlsSecurityProfile)
      2. Validate the connection to make sure that the connection uses TLS v1.1
      a. From one of the nodes execute:

      1. echo | openssl s_client -connect <ip>:<port> --tls1_1

      Actual results:
      ---------------
      With openssl results the cipher is NONE. This means no TLS v1.1 is supported.

      Expected results:
      -----------------
      With openssl results, TLS v1.1 should be supported

      Additional info:
      -----------------
      Simone has already investigated in to this issue.
      Here are some information about RCA:
      <snip>
      In the downstream build we have a file named /etc/crypto-policies/back-ends/opensslcnf.config
      which forces TLS.MinProtocol = TLSv1.2
      </snip>

              stirabos Simone Tiraboschi
              sasundar@redhat.com Satheesaran Sundaramoorthi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: