Dr. Stephen Henson d0edffc7da FIPS algorithm blocking. ... Non FIPS algorithms are not normally allowed in FIPS mode. Any attempt to use them via high level functions will return an error. The low level non-FIPS algorithm functions cannot return errors so they produce assertion failures. HMAC also has to give an assertion error because it (erroneously) can't return an error either. There are exceptions (such as MD5 in TLS and non cryptographic use of algorithms) and applications can override the blocking and use non FIPS algorithms anyway. For low level functions the override is perfomed by prefixing the algorithm initalization function with "private_" for example private_MD5_Init(). For high level functions an override is performed by setting a flag in the context.		2005-01-26 20:00:40 +00:00
..
asm	Make MD5 assembler code able to handle messages larger than 2GB on 32-bit	2003-09-27 22:14:47 +00:00
.cvsignore
Makefile	Don't use $(EXHEADER) directly in for loops, as most shells will break	2004-11-02 23:53:31 +00:00
md5.c	Make sure not to declare a clashing read() for DJGPP.	2003-01-13 15:35:27 +00:00
md5.h	FIPS algorithm blocking.	2005-01-26 20:00:40 +00:00
md5_dgst.c	FIPS algorithm blocking.	2005-01-26 20:00:40 +00:00
md5_locl.h	Make sure OPENSSL_SYS_ macros are defined, and in md5_locl.h, switch	2002-12-28 02:30:26 +00:00
md5_one.c	Windows CE updates, contributed by Steven Reddie <smr@essemer.com.au>	2002-12-03 14:21:32 +00:00
md5s.cpp
md5test.c	Have all tests use EXIT() to exit rather than exit(), since the latter doesn't	2002-11-28 18:57:30 +00:00