(at least hopefully :-)) been fixed.

Reports seem to show that asm/mips3.s has faults.  To be investigated, but let's avoid using it in the mean time

variables and disable the Alpha assembler for now, since it has been
shown to fail.

The Alpha failure can be shown by adding the following numbers:

FFFFFFFFFFFFFF0000FF2E00000000EBFFFFFF0000D1
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF46FFE0FFFF0000

The result is:

1FFFFFFFFFFFEFF0000FF2E0000000032FFE0FEFF00D1

The result should really be:

1FFFFFFFFFFFFFF0000FF2E0000000032FFE0FEFF00D1

there's no need fooling ourselves, it's the gnu-shared method that we
should use.  Do it for Solaris to begin with.

New cofiguration for Unixwre and SCO,with slightly better granularity.  Contributed by Tim Rice <tim@multitalents.net>

to create a symbol table).

Sun patches such as 109147-06 probably fix this problem,
but we can easily avoid it.

Submitted by Brad Dominy <jdominy@darwinuser.org>

functions on platform were that's the best way to handle exporting
global variables in shared libraries.  To enable this functionality,
one must configure with "EXPORT_VAR_AS_FN" or defined the C macro
"OPENSSL_EXPORT_VAR_AS_FUNCTION" in crypto/opensslconf.h (the latter
is normally done by Configure or something similar).

To implement a global variable, use the macro OPENSSL_IMPLEMENT_GLOBAL
in the source file (foo.c) like this:

	OPENSSL_IMPLEMENT_GLOBAL(int,foo)=1;
	OPENSSL_IMPLEMENT_GLOBAL(double,bar);

To declare a global variable, use the macros OPENSSL_DECLARE_GLOBAL
and OPENSSL_GLOBAL_REF in the header file (foo.h) like this:

	OPENSSL_DECLARE_GLOBAL(int,foo);
	#define foo OPENSSL_GLOBAL_REF(foo)
	OPENSSL_DECLARE_GLOBAL(double,bar);
	#define bar OPENSSL_GLOBAL_REF(bar)

The #defines are very important, and therefore so is including the
header file everywere where the defined globals are used.

The macro OPENSSL_EXPORT_VAR_AS_FUNCTION also affects the definition
of ASN.1 items, but that structure is a bt different.

The largest change is in util/mkdef.pl which has been enhanced with
better and easier to understand logic to choose which symbols should
go into the Windows .def files as well as a number of fixes and code
cleanup (among others, algorithm keywords are now sorted
lexicographically to avoid constant rewrites).

Define the OPENSSL_NO_* macros as NO_* macros for the sake of applications thathaven't yet been changed

missed any.

This compiles and runs on Linux, and external applications have no
problems with it.  The definite test will be to build this on VMS.

It's still inconsistent - probably better to undo the whole OPENSSL_NO_* thing.

sure they are available in opensslconf.h, by giving them names starting
with "OPENSSL_" to avoid conflicts with other packages and by making
sure e_os2.h will cover all platform-specific cases together with
opensslconf.h.

I've checked fairly well that nothing breaks with this (apart from
external software that will adapt if they have used something like
NO_KRB5), but I can't guarantee it completely, so a review of this
change would be a good thing.

<t-matsuu@protein.osaka-u.ac.jp>

Denis Beauchemin <Denis.Beauchemin@Courrier.USherb.ca>)

Fix PKCS7 and PKCS12 memory leaks.

Initialise encapsulated content type properly.

options.  This is so mk1mf.pl can pick it up from Makefile.

Also, define a second debugging configuration without assembler.

First tentative impementation of Kerberos 5 cryptos and keys for SSL/TLS.  Implemented by Vern Staats <staatsvr@asc.hpc.mil>, further hacked and distributed by Jeffrey Altman <jaltnab@columbia.edu>

away now...

passed down to ld as GNU cc.

environment variable, SHLIB_PATH.  This change makes that possible.

Submitted by Albert Chin-A-Young <china@thewrittenword.com>

Suggested by Albert Chin-A-Young <china@thewrittenword.com>

little-endian MIPS.
Submitted by Ralf Baechle <ralf@uni-koblenz.de>

At the same time, add VMS support for Rijndael.

you should defined _THREAD_SAFE (I found that in an include file, and
that's what everybody tells me) or _THREADSAFE (that's what the gcc
manual says in the FreeBSD-specific section), so I defined both, just
to be safe.

N.B.: This has not been tested at all, that's my next step.