Windows changes that detects if multibyte characters are available and
deals with them properly.

Contributed by Andy Polyakov <appro@fy.chalmers.se>

NUL-teminated at all times, and that we don't make unneeded calls to
free().

instead of local time.

I also used this opportunity to clean up some out-of-date targets and
re-group targets by OS.

we were mislead by _MSC_VER macro, which is defined by *all* Windows
Microsoft compilers.

Submitted by: Nils Larsch

(suggested by Adam Young <ayoung@cigital.com>)

Submitted by: Nils Larsch

(incidently, this also tells VMS that there exists a new symbol in the
SSL library)

we need to have them among the symbols that should appear in the
transfer table, at least on VMS (and it wouldn't surprise me if
Windows would whine as well).

Lucky me, I had prepared for this :-).

identities disabled.

Don't have a constant that you're going to assign to, that's just
plain stupid (I was the stupidhead here...).

linux-x86_64 target.

Now we have directory reading capabilities for VMS as well, and all
of it in a fairly general manner.

_stricmp() on that platform, use the appropriate header file for it,
<string.h>.
o_str.h: we only want to get size_t, which is defined in <stddef.h>.

Philippe Bougeret <philippe.bougeret@freesbee.fr> notified us about Windows
not having a <strings.h>

ec_curve.c (unify comments, etc).

Submitted by: Nils Larsch
Reviewed by: Bodo Moeller, Geoff Thorpe

Add a note as to how these functions do not always return the key size, and
how one can deal with that.

PR: 907

C code yet...

module name both SHA-256 and SHA-512 are supported.

performance improvement. Make module more gcc friendly and clarify
copyright issues for division routine.

PR: 499

there's no need for a larger BUFSIZE any more...

PR: 904

PR: 904

The changes have been mailed to <crypt@bis.doc.gov> as well.

PR: 903