distinction (which does not work well because if CRYPTO_MDEBUG is
defined at library compile time, it is not necessarily defined at
application compile time; and memory debugging now can be reconfigured
at run-time anyway).  To get the intended semantics, we could just use
the EVP_DigestInit_dbg unconditionally (which uses the caller's
__FILE__ and __LINE__ for memory leak debugging), but this would make
memory debugging inconsistent.  Instead, callers can use
CRYPTO_push_info() to track down memory leaks.

distinction (which does not work well because if CRYPTO_MDEBUG is
defined at library compile time, it is not necessarily defined at
application compile time; and memory debugging now can be reconfigured
at run-time anyway).  To get the intended semantics, we could just use
the EVP_DigestInit_dbg unconditionally (which uses the caller's
__FILE__ and __LINE__ for memory leak debugging), but this would make
memory debugging inconsistent.  Instead, callers can use
CRYPTO_push_info() to track down memory leaks.

Also fix indentation, and add OpenSSL copyright.

Submitted by: "Brian Havard" <brianh@kheldar.apana.org.au>

      [DR]SA_up  =>  [DR]SA_up_ref

is a bad idea if OPENSSL_OPENBSD_DEV_CRYPTO is not defined

Submitted by: "Brian Havard" <brianh@kheldar.apana.org.au>

counts in DH, DSA, and RSA structures. Instead they use the new "***_up()"
functions that handle this.

problems with leaks and uninitialised structures.

sourcecode (including fgrep)

(Latin for "comments", anyone?)

OpenBSD /dev/crypto (this will be revamped later when the appropriate machinery
is available).