Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
RichieMarkham
Beginner
Beginner

PAM agent v7.1.0.1.25 SELinux policy failure (rsapolicy.pp)

I've attached the install log.  The PAM agent works fine regardless of the errors, but I would like to address the SELinux policy issue.

 

This is the main error excerpt:

 

**********************************************************************
*         Adding label for pam_securid.so                            *
ValueError: File spec /lib64/security//pam_securid.so conflicts with equivalency rule '/lib64 /usr/lib'; Try adding '/usr/lib/security//pam_securid.so' instead
*         Adding label for /var/ace directory                        *
                                                                      
*         Creating rsapolicy.pp policy file                          *
Compiling targeted rsapolicy module
/usr/bin/checkmodule:  loading policy configuration from tmp/rsapolicy.tmp
/usr/bin/checkmodule:  Module name local is different than the output base filename rsapolicy
make: *** [tmp/rsapolicy.mod] Error 1
libsemanage.map_file: Unable to open rsapolicy.pp
 (No such file or directory).
libsemanage.semanage_direct_install_file: Unable to read file rsapolicy.pp
 (No such file or directory).
semodule:  Failed on rsapolicy.pp!
**********************************************************************

 

OS is RHEL 7.3

 

Installed Packages
selinux-policy-devel.noarch                                     3.13.1-102.el7_3.16                                      @rhel-7-server-rpms
policycoreutils-devel.x86_64                                        2.5-11.el7_3                                         @rhel-7-server-rpms
Labels (1)
0 Likes
2 Replies
LukaKodric
Trusted Contributor
Trusted Contributor

Did you do this?


# semanage fcontext -a -t var_auth_t "/var/ace(/.*)?"
# restorecon -R -v /var/ace

0 Likes
RichieMarkham
Beginner
Beginner

I just followed the readme for the install.   Somethings up w/the script and I suppose changes in RHEL 7.3.

0 Likes