Come on RSA you can do better then this.
I am trying to avoid underhanded security comment about using SELinux to protect key assets of the company...
I worked with Joe Lucchesi, to get this pam module to work with SELinux. Joe was having problems with sshd working with the pam module. He was getting execstack errors. Turns out the pam_securid.so file was shipped with the execstack flag turned on. Execstack is a dangerous protection to allow a domain, since it turns off protection against buffer overflow attacks. Most app never need this access.
execstack -c /lib64/security/pam_securid.so
Cleared the flag. And allowed sshd to get past this AVC. Whatever is causing this flag to be set, the build procedure or installation needs to be fixed.
The next problems we hit was pam_securid seems to be running netstat under the covers. I recall we had this problem with the Netscape Certificate libraries. They used to execute netstat in order to generate entropy when using certificates, so I figure this is what is going on here. I also see the sshd executing ps? Probably for the same reason.
RSA guys please use /dev/urandom and /dev/random.
We turned off the use of netstat in our libraries years ago. Using netstat and ps causes me to have to allow login programs to search /sys/net and because of bugs in our kernel add a dontaudit for sys_ptrace.
Finally secureid uses /var/ace to store its authorization content. This should probably be under /var/lib/ace, I have added a label for this directory
This should allow the pam_securid module to use the content in this directory.
Now Joe can run his pam_securid.so on his machine in enforcing mode with a small custom module until we push updates to fix the problem.
Bottom line. If you are a third party and you are having problems running your tools with SELinux, please, please contact me or Red Hat and lets work through the problems, and give our users a better experience.