| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
fixing a dead link reported by jmc@.
Only about half of X509_VERIFY_PARAM is documented so far,
and the extensible lookup table feels like one of the more
arcane features and probably not the next thing to document.
|
|
|
|
|
|
|
| |
jmc@ reported that X509_LOOKUP_hash_dir(3) references it.
Even though OpenSSL does not document it, given that it is used for
file names that users have to create, it is sufficiently exposed
to users to be worth documenting.
|
|
|
|
|
|
|
|
|
|
|
| |
Not documented by OpenSSL, but listed in <openssl/x509_vfy.h>
and referenced from X509_LOOKUP_hash_dir(3), and clearly more
important than the latter. Fixes three dead links reported by jmc@.
Most of the information from SSL_CTX_load_verify_locations(3) should
probably be moved here, but not all, since the SSL page also talks
about SSL servers and clients and the like. As i'm not completely
sure regarding the boundaries, i'm leaving that as it is for now.
|
|
|
|
|
|
|
| |
and X509_STORE_add_lookup(3) reported by jmc@.
Even though these functions are public, they seem more useful internally
than for application programs, so now is not the time to document them.
|
|
|
|
|
|
|
| |
function that had the the sole purpose of discouraging its use.
Not talking about it at all discourages using it even more.
Dangling cross reference reported by jmc@.
|
|
|
|
| |
and sprinkle cross references instead; more work is obviously needed here
|
|
|
|
|
|
| |
The safestack stuff is the most ill-designed user interface i have
seen so far in OpenSSL. It looks positively undocumentable.
At least i'm not trying to document it right now.
|
|
|
|
|
|
|
|
|
| |
that wasn't accompanied by any related information. Reported by jmc@.
There are a dozen functions handling X509_PURPOSE objects, all
undocumented, a host of defines, and it seems that a callback is
required. So this seems complicated, i doubt that is much used
in practice, and i'm not diving into it at this point in time.
|
|
|
|
|
|
|
|
|
| |
and refer readers to the header file instead.
I'm not convinced customized prompting is such a bright idea, it
feels somewhat like overengineering, so i'm not documenting it right
now. People who really feel compelled to roll their own prompting
can go read the source code.
|
|
|
|
|
|
|
|
|
| |
and just use .Fn for now.
Not counting constructors, destructors, decoders, encoders, and
debuggers, six out of 24 public functions operating on PKCS7 objects
are currently documented. I'm not documenting the remaining 18 ones
at this point in time.
|