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

warning: run-time library vs. compile-time header version mismatch: OpenSSL 3.5.0 may not be compatible with OpenSSL 3.2.0

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • None
    • CentOS Stream 9
    • postfix
    • None
    • None
    • None
    • Hide
      warning: run-time library vs. compile-time header version mismatch: OpenSSL 3.5.0 may not be compatible with OpenSSL 3.2.0. internet searches indicate that postfix may have been compiled with a 3.2.0 version of OpenSSL and the system is running 3.5.0. The searches propose to recompile postfix with OpenSSL using 3.5.0
      Show
      warning: run-time library vs. compile-time header version mismatch: OpenSSL 3.5.0 may not be compatible with OpenSSL 3.2.0. internet searches indicate that postfix may have been compiled with a 3.2.0 version of OpenSSL and the system is running 3.5.0. The searches propose to recompile postfix with OpenSSL using 3.5.0
    • rhel-net-perf
    • None
    • None
    • CentOS Stream
    • None
    • None
    • None
    • x86_64
    • None

      What were you trying to do that didn't work?

      doing IMAPS in postfix.

      What is the impact of this issue to you?

      Cannot complete migration off old server to new server

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?: happens every time

      Steps to reproduce

      1. connect using IMAPS
      2.  
      3.  

      Expected resultsget a connection and send email

      Actual results cannot connect due to mismatch in openssl 

              jskarvad Jaroslav Škarvada
              gguldens56 Greg Guldenschuh (Inactive)
              Jaroslav Škarvada Jaroslav Škarvada
              Robin Hack Robin Hack
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: