[krbdev.mit.edu #6125] krb5_cccol_lock/unlock should not have hardcoded mutex names

Justin Anderson via RT rt-comment at krbdev.mit.edu
Mon Sep 22 13:17:36 EDT 2008


e.g. krb5int_cc_file_mutex, krb5int_mcc_mutex, krb5int_krcc_mutex should not be explicitly 
named in the cccol locking functions. 

It would be less fragile to add pertype lock and unlock calls to each cache type's ops vector and 
make krb5_cccol_lock/unlock iterate the types.



More information about the krb5-bugs mailing list