Description of problem:
pam_fprintd brings in an old pthread library which causes kerberos library failure in trying to obtain a mutex. when that fails, user kerberos cache cannot be created. 

pam_fprintd being in PAM configuration will be loaded. it brings in an older libpthread to resolve its symbol requirements. 

Kerberos library gss_krb5_copy_ccache() call by openssh now fails when it tries to call pthread_mutex_lock(). 

if pam_fprintd is loaded before an aditional authentication module , it loads its old pthread library which emits the same symbol, so our call winds up calling its mutex function which returns error. 

Version-Release number of selected component (if applicable):
RHEL 6.4  pam_fprintd module


removing the fprintd  module from pam stack allows this to function as expected.

How reproducible:

pam_fprintd being in PAM configuration will be loaded. it brings in an older libpthread to resolve its symbol requirements. 

Kerberos library gss_krb5_copy_ccache() call by openssh now fails when it tries to call pthread_mutex_lock(). 

Steps to Reproduce:
1. Standard RHEL 6 install
2. Add a kerberos Authentication module into Pam stack AFTER fprintd
3. SSH into the system using SSO and then check for existing TGT. It will not be present.

Actual results:
TGT is not present for use in additional authentication

Expected results:

TGT should be present for use in additional authentication
Additional info: