| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
function EVP_MD_CTX_init(3) and talk about EVP_MD_CTX_new(3) instead.
This is similar in spirit to OpenSSL commit 25191fff (Dec 1, 2015),
but i'm also mentioning EVP_MD_CTX_reset(3), slightly reordering some
sentences in a more systematic way, and improving some related wordings
to be more precise and read better.
|
|
|
|
|
|
|
| |
This uses the same language in most manuals mentioning the obsolete
ENGINE parameters. Make it clear that it is always ignored and that
NULL should be passed. Always call it engine instead of a mix of e
pe, impl, eng.
|
|
|
|
| |
where that information was missing.
|
|
|
|
| |
references were already given below RETURN VALUES right above
|
|
|
|
|
|
| |
EVP_MD_CTX_free() instead if the goal is to avoid leaking memory.
From my corresponding upstream commit, reminded by schwarze
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The comment in EVP_DigestInit.pod is:
"EVP_MD_pkey_type() returns the NID of the public key signing algorithm
associated with this digest. For example EVP_sha1() is associated with
RSA so this will return NID_sha1WithRSAEncryption. Since digests and
signature algorithms are no longer linked this function is only retained
for compatibility reasons."
So there is no link anymore.
From <paul dot dale at oracle dot com>
via OpenSSL commit 79b49fb0 Mar 20 10:03:10 2018 +1000
|
|
|
|
| |
on the web, so fix up SSLeay HISTORY accordingly
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|