In my wanderings as a Samba4 developer, I've been trying to remove a nasty piece of code that 'locks' the krb5 replay cache. My question to the Heimdal list is 'should this be the responsibility of the krb5 libs?'. Currently, as far as I can tell, standard fopen ()/fwrite() calls are used to manipulate the krb5 replay cache, but nothing is done to tell if there are concurrent writes. Is this correct? Is it viable for krb5 to be extended to provide this locking, in a way a configure test could pick up (so I can at least conditionally remove Samba's locking), and have it consistent with other apps that Samba may be sharing with on a system?. Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net
This is a digitally signed message part