however for different reasons. This separation should prevent the win32
build from interpreting evptests.txt as source code.

name. The implementations already use this anyway.

not implemented. (Bug reported by Martin Szotkowski)

This also changes the non-"_ex" versions to defer directly to
EVP_CipherInit_ex() rather than EVP_CipherInit() to avoid an unecessary
level of indirection.

it to be defined on all platforms whether or not it is of any practical
use on them. This also resolves linker problems on "special" platforms,
such as win32.

Martin Szotkowski.

Submitted by Massimo Santin <msantin@santineassociati.com>.

VMS as well :-).

types.h to ossl_typ.h.
Also, it seems like krb5 was forgotten in some places.

types.h to ossl_typ.h.

BIO buffer instead of hard coding it as 8.

*sigh* habit...

Let's use sk_ENGINE_CLEANUP_ITEM_pop_free() instead.

a pointer any more).

the compiler not to warn about that.

needed.

of the stack, and the (void *) type used in the underlying sk_***
functions.  However, declaring a STACK_OF(type) where type is a *function*
type implicitly involves casts between function pointers and data pointers.
That's a no-no. This changes the ENGINE_CLEANUP handling to use a regular
data type in the stack.

a few items however, most of the details are deferred to the
crypto/engine/README file.

ciphers.

that way.  Synchronise s_time with these changes.

algorithms present in all loaded ENGINEs. The result is that if any of
those ENGINEs successfully initialises, and the ENGINE_TABLE_FLAG_NOINIT
flag isn't set, then they will always be used (and cached as defaults) in
preference to software implementations. Ie. accidental auto-detection of
acceleration hardware :-)

This change stops all implementations being automatically registered in
"openssl" sub-commands, so that the "setup_engine()" handler in apps.c
controls which ENGINEs are registered for use. A special case has been
added that will revert to this "auto-detect" logic, ie. if the "-engine"
switch is used as;
   -engine auto

Show timing parameters and timing functions used.
It looks like some Linuxen have very weird settings for CLK_TCK.  I'm
very unsure about this change and will investigate further.