| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
removed/renamed a long time back.
|
|
|
|
|
|
| |
code. We removed SSLv2/SSLv3 a long time ago...
Discussed with doug@
|
|
|
|
|
|
|
|
| |
from the OpenSSL manual and from code inspection.
Use my own Copyright and license because no Copyright-worthy amount
of text from OpenSSL remains.
And, no, these functions do *NOT* check private keys, not at all.
|
|
|
|
|
| |
from Richard Levitte <levitte at openssl dot org>
via OpenSSL commit e9c9971b Jul 1 18:28:50 2017 +0200
|
|
|
|
|
| |
from Emilia Kasper <emilia at openssl dot org>
via OpenSSL commit 1e3f62a3 Jul 17 16:47:13 2017 +0200.
|
|
|
|
|
|
| |
stating that RSA_padding_check_PKCS1_type_2(3) is weak by design;
from Emilia Kasper <emilia at openssl dot org>
via OpenSSL commit 1e3f62a3 Jul 17 16:47:13 2017 +0200.
|
|
|
|
| |
dropping the secmem stuff that we don't want
|
|
|
|
| |
now also documents it, in OPENSSL_malloc.pod
|
|
|
|
| |
don't have, which implies renaming the file to EVP_PKEY_meth_get0_info.3
|
|
|
|
|
| |
from Rich Salz <rsalz at openssl dot org>
via OpenSSL commit 1722496f Jun 8 15:18:38 2017 -0400
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. mention three additional functions for stitched ciphers
from Steven Collison <steven at raycoll dot com>
via OpenSSL commit 209fac9f Mar 28 12:46:07 2017 -0700
2. fix wrong data type of an automatic variable in an example
from Paul Yang <paulyang dot inf at gmail dot com>
via OpenSSL commit 719b289d May 22 23:18:45 2017 +0800
3. fix memory leak in sample encryption code and check return value of fopen
from Greg Zaverucha <gregz at microsoft dot com>
via OpenSSL commit 519a5d1e Jun 27 17:38:25 2017 -0700
|
| |
|
|
|
|
|
| |
minor improvements. Mostly from Todd Short <tshort at akamai dot com>
via OpenSSL commit cf37aaa3 Aug 4 11:24:03 2017 +1000.
|
|
|
|
| |
from Rich Salz, OpenSSL commit a95d7574, July 2, 2017
|
|
|
|
|
|
|
|
|
| |
the OpenSSL manual page committed on July 27, 2017, and on source
code inspection. Use my own Copyright and license because no
copyright-worthy amount of text from OpenSSL remains.
NOTA BENE:
BUGS Most aspects of the semantics considerably differ from OpenSSL.
|
|
|
|
|
| |
found with regress/usr.bin/mandoc/db/dbm_dump;
OK jmc@
|
| |
|
| |
|
| |
|
|
|
|
| |
it returns "len", which is a size_t value, as an int...
|
| |
|
|
|
|
| |
ok jsing@
|
|
|
|
| |
from Dr. Stephen Henson <steve@openssl.org>, OpenSSL commit d218f3c3
|
|
|
|
| |
from Emilia Kasper <emilia at openssl dot org>, OpenSSL commit 4ac139b4
|
| |
|
| |
|
| |
|
|
|
|
| |
from Rich Salz <rsalz@openssl.org>, OpenSSL commit 3e5d9da5 etc.
|
|
|
|
|
| |
from Emilia Kasper <emilia@openssl.org>, OpenSSL commit 80770da3,
tweaked by me
|
|
|
|
| |
from Richard Levitte <levitte@openssl.org>, OpenSSL commit cdd6c8c5
|
|
|
|
| |
from Matt Caswell <matt@openssl.org>, OpenSSL commit b41f6b64
|
|
|
|
| |
from Matt Caswell <matt@openssl.org>, OpenSSL commit b41f6b64
|
|
|
|
| |
from Alexander Koeppe via OpenSSL commit bb6c5e7f
|
|
|
|
| |
from Todd Short <tshort@akamai.com> via OpenSSL commit 52ad5b60
|
|
|
|
|
| |
in commit 2ca2e917. Document it here, too, but do not use their
text. Be more concise and more precise at the same time.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and document ERR_asprintf_error_data as their replacement.
ok jsing@, ingo@
|
| |
|
|
|
|
| |
jsing@ confirmed that these are public and worth documenting.
|
| |
|
|
|
|
| |
jsing@ confirmed that these macros are public and worth documenting.
|
|
|
|
|
|
|
| |
and BN_RECP_CTX_init(3). They are not only deprecated but so
dangerous that they are almost unusable. I found these scary
traps while reading the code in order to document BN_set_flags(3).
While here, delete ERR_get_error(3) from SEE ALSO.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
jsing@ confirmed that this function is public and worth documenting.
This page needs much more work, it is outrageously incomplete and
unclear. For example, it remains unexplained what error strings
are, what "registering" means and what the benefit for the application
is, what happens if it is not done, or what happens if an error
occurs after calling ERR_free_strings(3). I tried to read the code,
but it is so contorted that i postponed that work. For example,
it looks like there are hooks for applications to replace the
functions used for registering strings by other, application-supplied
functions, and, of course, there are many levels of macro and
function wrappers.
For now, i only documented the most obvious BUGS.
|
|
|
|
| |
jsing@ confirmed that it is a public function worth documenting
|
| |
|
| |
|
| |
|
| |
|