Uploaded image for project: 'Community Package Repository'
  1. Community Package Repository
  2. CPR-675

EL 6 puppet-client-tools linked against old SSL library

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Packaging
    • Labels:
      None
    • Template:
    • Team:
      Release Engineering
    • Sprint:
      Release Engineering Kanban
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      The RPM puppet-client-tools-1.2.6-1.el6.x86_64 appears to be built on an old / out dated EL system, and it is somehow linking binaries against OpenSSL 1.0.0:

      $ ldd /opt/puppetlabs/client-tools/bin/puppet-query
       linux-vdso.so.1 => (0x00007ffd04737000)
       libssl.so.1.0.0 => not found
       libcrypto.so.1.0.0 => not found
       libdl.so.2 => /lib64/libdl.so.2 (0x00007f24fdb93000)
       librt.so.1 => /lib64/librt.so.1 (0x00007f24fd98b000)
       libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f24fd76d000)
       libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f24fd557000)
       libc.so.6 => /lib64/libc.so.6 (0x00007f24fd1c3000)
       /lib64/ld-linux-x86-64.so.2 (0x000000357fc00000)

       

      Should be at least 1.0.1e:

      $ ls -ld /usr/lib64/libssl.so.1.0.1e /usr/lib64/libcrypto.so.1.0.1e 
      -rwxr-xr-x 1 root root 1969952 Sep 27 2016 /usr/lib64/libcrypto.so.1.0.1e
      -rwxr-xr-x 1 root root 448344 Sep 27 2016 /usr/lib64/libssl.so.1.0.1e

       

      This is slightly similar to CPR-662 where the Ubuntu binary is expecting an OpenSSL symbol that's too old to what's on the operating system.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                molly.waggett Molly Waggett
                Reporter:
                lukebigum Luke Bigum
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support