How is an application supposed to know if a Kerberos library isthread safe?
jaltman at columbia.edu
Mon Dec 20 12:30:14 EST 2004
Jeffrey Altman wrote:
> Sam Hartman wrote:
>> I think a solution is needed to this problem. My head hurts when I
>> think about reasonable general solutions to this problem so let's
>> consider something specific to this one issue.
> I am going to propose the follow prototypes for functions which can
> provide a run-time answer to the question of thread safety.
> krb5_boolean KRB5_CALLCONV krb5_is_thread_safe(krb5_context context);
> OM_uint32 KRB5_CALLCONV gss_krb5_is_thread_safe(void *kctx);
> Jeffrey Altman
So far the only comment I have received is that
gss_krb5_is_thread_safe() should not take an argument. Therefore, the
revised proposal is:
krb5_boolean KRB5_CALLCONV krb5_is_thread_safe(krb5_context context);
OM_uint32 KRB5_CALLCONV gss_krb5_is_thread_safe(void);
Heimdal has agreed to add these functions when MIT does.
Any other opinions? Does anyone object? If not, I will add them today.
More information about the krbdev