this integration with a web-server using CryptoSwift engine code with RSA
and DSA certificates (and with EDH cipher suites).

CryptoSwift (this currently only does signing, verification will be
hooked in shortly).

a bit, so bring libeay.num up to date.

coming up soon after some more tinkering.

Submitted by:
Reviewed by:
PR:

already been done for RSA. The others (DSA + RAND) will probably follow
in the near future too, but DH is easiest to test with RSA because one
can just force the use of the EDH cipher-suites.

"engine" to use.

than (RSA_METHOD *) required a couple of functions to change shape. I
didn't really pick the best shape to change RSA_set_method into though. :-)

There's nothing really appropriate to return from RSA_set_method; the
temptation to return an "old handle" fails when you consider that the
caller might ignore the return value and so botch up the reference
counting, this wasn't an issue before because there was no reference
counting.

to ENGINE_new (and ENGINE_get_struct_size).

This was a bad idea in the first place, in particular it would have made
it trickier to implement error-handling, particularly when shutting down
third-party shared libraries etc.

README.  Oh, and a test program.

patches that Geoff had in a patch file in his play directory.

NOTE for openssl-cvs:  THIS IS A CVS BRANCH (BRANCH_engine).  IT IS
NOT FOR THE FAINTHEARTED TO PLAY WITH.  The code works as it is, but
it's not at all sure it ends up in the OpenSSL distributio in this
form, so do not get dependent on it!

Those rsyncing the repository are considered warned!

Call dh_tmp_cb with correct 'is_export' flag.

Avoid tabs in CHANGES.

ASN1 encoding.

Submitted by: Arnaud De Timmerman <Arnaud.De.Timmerman@branchur.fr>

Contributed by SAKAI Kiyotaka <ksakai@kso.netwk.ntt-at.co.jp>

to adhere to are listed.  It should be regarded as a complement to
whatever is out on the web, including the docs in http://www.openssl.org/