[2132] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: krb5 thread safety

daemon@ATHENA.MIT.EDU (Sam Hartman)
Fri Dec 20 17:21:16 1996

To: Kamen Lozev <lozev+@andrew.cmu.edu>
Cc: krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 20 Dec 1996 17:20:51 -0500
In-Reply-To: Kamen Lozev's message of Fri, 20 Dec 1996 16:40:57 -0500 (EST)

>>>>> "Kamen" == Kamen Lozev <lozev+@andrew.cmu.edu> writes:

    Kamen> hi guys, congratulations on release 1.0.

	Thanks much.  

    Kamen>   is the krb5
    Kamen> library thread safe in this release?  if not when do you
    Kamen> think it will be?

	The krbdev@mit.edu mailing list is not an appropriate forum
for this type of question.  It would be more reasonable to post such
questions to comp.protocols.kerberos or kerberos@mit.edu.  (They are
the same list.)
	The answer to your question is that while the library has very
little static data, there are certain aspects of the published
interface and of the implementation that make it sub-optimal for
threaded programming.  I don't think that making the library thread
safe is a real high priority for us, but it is something that we
recognize as being a good thing.

	As always, we accept well-written, well-designed,
freely-redistributable code to implement useful features like thread
safety.  (I'm not trying to force you to write it, but often the free
software community works because people write code they need and give
it to other.s)


    Kamen> thanks.

    Kamen> kamen

home help back first fref pref prev next nref lref last post