That's correct, and it's stated in the readme file. You should not access the same Crypto++ object from multiple threads without synchronization (because the object may have buffers that are used as temporary working space to avoid having to repeatedly allocate and deallocate memory). Alternatively, make a copy of the object for each thread.
On Wed, Nov 20, 2002 at 06:28:40PM +0100, Dejan Maksimovic wrote: > > Hi, > > I am using CryptoPP in a driver. In WinNT/2K/XP it is possible > to have multiple file objects for the same file - and they may be > accessed randomly. > Are classes thread safe, so that I can safely use the same class > in separate threads, for the SAME data? From the implementation, it > seems that some internal variables might not be thread safe... > > -- > Kind regards, Dejan M. www.alfasp.com > E-mail: [EMAIL PROTECTED] ICQ#: 56570367 > Alfa File Monitor - File monitoring library for Win32 developers. > Alfa File Protector - File protection and hiding library for Win32 > developers. >
