The "sshd: /usr/seos/lib/libcryptscr.so: wrong ELF class: ELFCLASS32" log is occurring when connecting to the PAMSC server with sftp /sshd

Products

• CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

The following log is occurring when connecting to a PAMSC endpoint via sftp or sshd.

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 801593 auth.error] /opt/CA/PAMSC/lib/libcryptscr.so: ld.so.1: sshd: /opt/CA/PAMSC/lib/libcryptscr.so: wrong ELF class: ELFCLASS32

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 801593 auth.error] /opt/CA/PAMSC/lib/64/libcryptscr.so: ld.so.1: sshd: /opt/CA/PAMSC/lib/64/libcryptscr.so: open failed: No such file or directory

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 218643 auth.error] /opt/CA/PAMSC/lib/64/libcryptscr.so: + B

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 834567 auth.error] open_module[0:/etc/pam.d/other]: stat(/usr/lib/security//64/pam_dhkeys.so.1) failed: No such file or directory

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 301792 auth.warning] libpam ignoring missing legacy module entry /usr/lib/security//64/pam_dhkeys.so.1 in /etc/pam.d/other. Remove the configuration file entry or re-install the module.

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 834567 auth.error] open_module[0:/etc/pam.d/other]: stat(/usr/lib/security//64/pam_dhkeys.so.1) failed: No such file or directory

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 301792 auth.warning] libpam ignoring missing legacy module entry /usr/lib/security//64/pam_dhkeys.so.1 in /etc/pam.d/other. Remove the configuration file entry or re-install the module.

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 834567 auth.error] open_module[0:/etc/pam.d/other]: stat(/usr/lib/security//64/pam_dhkeys.so.1) failed: No such file or directory

 Jul 4 17:17:50 pamschost sshd[PID]: [ID 301792 auth.warning] libpam ignoring missing legacy module entry /usr/lib/security//64/pam_dhkeys.so.1 in /etc/pam.d/other. Remove the configuration file entry or re-install the module. 

Environment

PAM Server Control

Cause

This is a know issue with the GA build of the 14.0 PAMSC endpoint.

Resolution

The problem has been fixed in the code, please upgrade to the newest PAMSC 14.1 endpoint.

Additional Information

The newest PAMSC build can be found in the support link below.

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/release-announcements/CA-Privileged-Access-Manager-Server-Control-Endpoint-Compatibility-Matrix/16749