Richard Levitte 7f9c37457a To protect FIPS-related global variables, add locking mechanisms ... around them. NOTE: because two new locks are added, this adds potential binary incompatibility with earlier versions in the 0.9.7 series. However, those locks will only ever be touched when FIPS_mode_set() is called and after, thanks to a variable that's only changed from 0 to 1 once (when FIPS_mode_set() is called). So basically, as long as FIPS mode hasn't been engaged explicitely by the calling application, the new locks are treated as if they didn't exist at all, thus not becoming a problem. Applications that are built or rebuilt to use FIPS functionality will need to be recompiled in any case, thus not being a problem either.		2004-07-30 14:38:02 +00:00
..
.cvsignore	Ignore 'Makefile.save'	2004-05-12 10:07:20 +00:00
fingerprint.sha1	To protect FIPS-related global variables, add locking mechanisms	2004-07-30 14:38:02 +00:00
fips_rsa_eay.c	To protect FIPS-related global variables, add locking mechanisms	2004-07-30 14:38:02 +00:00
fips_rsa_gen.c	To protect FIPS-related global variables, add locking mechanisms	2004-07-30 14:38:02 +00:00
fips_rsa_selftest.c	Avoid compiler warnings.	2004-07-21 17:35:49 +00:00
Makefile	Make sure we don't try to loop over an empty EXHEADER. In the	2004-06-21 09:07:41 +00:00