don't crash and burn.

generated from the Unixly configuration file.

Makefile modifications, make test, etc. will appear later...

is subject to change as C implementation is added...

config and run-time support is added.
PR: 788
Submitted by: <dean@arctic.org>
Reviewed by: <appro>

Obtained from: http://arctic.org/~dean/crypto/rsa.html

use it.

Notified by Frédéric L. W. Meunier <0@pervalidus.tk> in PR 713

well.

Notified by Frank Kardel <kardel@acm.org> in PR 879.

Submitted by: Nils Larsch
Reviewed by: Geoff Thorpe

- update from current 0.9.7-stable CHANGES file:

  Now here we have "CHANGES between 0.9.7e and 0.9.8", and I hope
  that all patches mentioned for 0.9.7d and 0.9.7e actually are
  in the CVS HEAD, i.e. what is to become 0.9.8.

  I have rewritten the 'openssl ca -create_serial' entry (0.9.8)
  so that it explains the earlier change that is now listed (0.9.7e).

  The ENGINE_set_default typo bug entry has been moved from 0.9.8
  to 0.9.7b, which is where it belongs.

especially for AIX. But most important BIGNUM assembler implementation
submitted by IBM.

Submitted by: Peter Waltenberg <pwalten@au1.ibm.com>
Reviewed by: appro

additional contexts.

small key sizes seems to result from the code continually regenerating the
same prime value once the range is small enough. From my tests, this change
fixes the problem by setting an escape velocity of 3 repeats for the second
of the two primes.

PR: 874

proposed the change and submitted the patch, I jiggled it slightly and
adjusted the other parts of openssl that were affected.

PR: 867
Submitted by: Jelte Jansen
Reviewed by: Geoff Thorpe

PR:870

0.9.7-stable as well as HEAD (and doesn't apply to the 0.9.6-engine
variant).

some similar code elsewhere.

Thanks to Francesco Petruzzi for bringing this to my attention.

serial number plus 1 to the output file. Its purpose is to allow
serial number files to be initialized when random serial numbers
are used.

initial serial numbers.

PR: 842

days...  A little too much for my tests, currently...

else then at least so bc doesn't have problems parsing the output from
bntest :-).

consolidated these prior to committing).

dependencies of the OPENSSL_NO_DEPRECATED mode. This prevents dependencies
being reproduced for "deprecated" header behaviour when a developer doesn't
define the symbol (with the subsequent CVS wars that can ensue).

tree. This further reduces header interdependencies, and makes some
associated cleanups.

changes are the fallout). As this could break source code that doesn't
directly include headers for interfaces it uses, changes to recursive
includes are covered by the OPENSSL_NO_DEPRECATED symbol. It's better to
define this when building and using openssl, and then adapt code where
necessary - this is how to stay current. However the mechanism exists for
the lethargic.