This change resolves a number of problems and obviates multiple kludges.
A new feature is that you can now say "AES256" or "AES128" (not just
"AES", which enables both).

In some cases the ciphersuite list generated from a given string is
affected by this change.  I hope this is just in those cases where the
previous behaviour did not make sense.

Submitted by: Peter Sylvester

Submitted by: Peter Sylvester
Reviewed by: Bodo Moeller

Submitted by: Kaspar Brand, Peter Sylvester

Submitted by: Douglas Stebila

PR: 1293

than zero will only result in pissing of some compilers...

unsigned...

Submitted by: Douglas Stebila

Submitted by: Douglas Stebila

Submitted by: Peter Sylvester

Submitted by: Peter Sylvester

Submitted by: Peter Sylvester

 - fix indentation
 - rename some functions and macros
 - fix up confusion between SSL_ERROR_... and SSL_AD_... values

Submitted by: Peter Sylvester

for locking code. The CRYPTO_LOCK_SSL_METHOD lock is now no longer used.

designed for that.  This removes the potential error to mix data and
function pointers.

Please note that I'm a little unsure how incorrect calls to the old
ctrl functions should be handled, in som cases.  I currently return 0
and that's it, but it may be more correct to generate a genuine error
in those cases.

eliminate some of the -Wcast-qual warnings (debug-ben-strict target)

Submitted by:
Reviewed by:
PR:

1. The already released version was 0.9.1c and not 0.9.1b

2. The next release should be 0.9.2 and not 0.9.1d, because
   first the changes are already too large, second we should avoid any more
   0.9.1x confusions and third, the Apache version semantics of
   VERSION.REVISION.PATCHLEVEL for the version string is reasonable (and here
   .2 is already just a patchlevel and not major change).
tVS: ----------------------------------------------------------------------