[krbdev.mit.edu #7627] g_initialize.c build_MechSet potential to leak a lock

Greg Hudson via RT rt-comment at krbdev.mit.edu
Wed May 1 20:05:16 EDT 2013


In January 2012 we agreed to update our portability assumptions to include 
the assumption that locking a non-recursive mutexes will never fail.  We 
haven't updated the code to remove all of the conditionals yet, but it's 
not really worth fixing this logic bug.


More information about the krb5-bugs mailing list