[3744] in Kerberos-V5-bugs
[krbdev.mit.edu #1303] thread safety in mit-krb5 libraries
daemon@ATHENA.MIT.EDU (Ken Raeburn via RT)
Tue Jan 7 23:13:56 2003
Message-Id: <rt-1303-3860.11.6519351181972@krbdev.mit.edu>
In-Reply-To: <rt-1303@krbdev.mit.edu>
From: "Ken Raeburn via RT" <rt-comment@krbdev.mit.edu>
Reply-To: rt-comment@krbdev.mit.edu
To: krb5-prs@mit.edu
Errors-To: krb5-bugs-admin@mit.edu
Date: Tue, 7 Jan 2003 23:10:09 -0500 (EST)
Many changes are needed in the krb5 library (and others) to make the
code thread-safe.
Any non-const global variables need protection against simultaneous read
and write. (If a static-duration object can't be updated, it should
probably be const.)
File locking is per-process (at least under UNIX); when we do file
locking, we'll want it to effectively be per-thread.
This issue has been discussed in email (on krbdev?), and people at IBM
are supposed to be writing some code based on that discussion; just
making sure it gets listed here too....
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
http://mailman.mit.edu/mailman/listinfo/krb5-bugs
