| 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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
EVP_DigestSign{,Init,Update,Final}() and EVP_DigestVerify{Init,Update}()
always returned 1 for success and 0 for failure. EVP_DigestVerify()
and EVP_DigestVerifyFinal() can return -1 or -2, though.
Based on OpenSSL 1.1.1 56c59ddd99da05c2f30832cccaffb873a8481555
ok inoguchi
|
| |
|
| |
|
| |
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
removing parts that don't apply to OpenBSD.
|
|
|
|
| |
Correct a parameter type for EVP_DigestSignUpdate(3), from OpenSSL.
|
| |
|
|
|