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.

and make it work in non-interactive mode...

memory BIO (for example from SMIME_read_PKCS7 and detached data) avoid lots
of slow memory copies from the memory BIO by saving the content in a
temporary read only memory BIO.

PR: 989

environments.

PR: 998

really needed now, but may be needed in the future, who knows?).

Change the fingerprint accordingly.

besides, the implementation is bogus.

PR: 993

PR: 989
Submitted by: Doug Kaufman

PR: 924

PR: 949

doesn't pay off...

I change from -notall to -none synonym in do_irix-shared to improve backward
compatibility with IRIX 5.x.
PR: 987

message size limitations on 64-bit platforms.

a bug-fix for Win64/ia64.

shared context [because it's not PIC].